From nano at remap.ucla.edu Wed Feb 1 08:19:11 2017 From: nano at remap.ucla.edu (Alex Horn) Date: Wed, 1 Feb 2017 10:19:11 -0600 Subject: [Ndn-interest] IOT Blockchain Message-ID: FYI http://www.coindesk.com/bosch-cisco-gemalto-and-more-tech-giants-team-for-blockchain-iot/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From lanwang at memphis.edu Wed Feb 1 18:20:16 2017 From: lanwang at memphis.edu (Lan Wang (lanwang)) Date: Thu, 2 Feb 2017 02:20:16 +0000 Subject: [Ndn-interest] Inter-domain routing In-Reply-To: References: Message-ID: Hi Charif, Our work on hyperbolic routing is intended to address global routing scalability in NDN. You can find the paper (V. Lehman, A. Gawande, R. Aldecoa, D. Krioukov, B. Zhang, L. Zhang, L. Wang, "An Experimental Investigation of Hyperbolic Routing with a Smart Forwarding Plane in NDN," in Proceedings of the IEEE IWQoS Symposium, June 2016?) at http://web0.cs.memphis.edu/~lanwang/paper/hr-iwqos-camera-ready.pdf. There are issues that are not addressed in this paper but are part of our ongoing research. Thanks. Lan On Jan 31, 2017, at 2:01 PM, Mahmoudi, Charif (IntlAssoc) > wrote: Hi, We are trying to address some of the inter-domain routing challenges in ICN. We are looking for pointers to existing efforts. We found solutions intra-domain efforts like NLSR (https://doi.org/10.1145/2491224.2491231 ) and CORBA (https://doi.org/10.1109/CCNC.2014.6994403 ). However, not as much on inter-domain routing. Is someone in the community is aware of past/ongoing efforts toward inter-domain routing, please send us some pointers. Thanks for your help, Charif _______________________________________________ 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 josh at caida.org Thu Feb 2 08:38:40 2017 From: josh at caida.org (Josh Polterock) Date: Thu, 2 Feb 2017 08:38:40 -0800 Subject: [Ndn-interest] Named Data Networking (NDN) Project Monthly Newsletter for January 2017 Message-ID: <20170202163840.GB77489@caida.org> Named Data Networking (NDN) Project Newsletter for January 2017 The NDN project team compiles and publishes this newsletter periodically to inform the community about recent activities, technical news, meetings, publications, presentations, code releases, and upcoming events. You can find these newsletters posted on the Named Data Networking Project blog. COMMUNITY OUTREACH * Registration remains open for NDNcomm at the University of Memphis March 23-24, 2017 immediately preceding IETF 98 in Chicago. The deadline to request travel grants is February 6, 2017. To register, point your browser at http://www.caida.org/workshops/ndn/1703/register.xml. You can find details regarding the developing meeting agenda and accomodations at http://www.caida.org/workshops/ndn/1703/. * Call for Hacks: we will hold the 4th NDN Hackathon immediately following NDNcomm on 25-26 March, 2017. Submission deadline: March 1, 2017 For more information please see http://4th-ndn-hackathon.named-data.net TECHNICAL NEWS * We released version 0.5.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.5.1/RELEASE_NOTES.html - for ndn-cxx library: http://named-data.net/doc/ndn-cxx/0.5.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.5.1/ - http://named-data.net/doc/ndn-cxx/0.5.1/ **NEW** PPA binary packages now include support for arm64, armhf, and ppc64el CPU architectures. * We released ndnSIM version 2.3, a new release of the NDN simulator. The new version includes the updated submodules of NFD and ndn-cxx (based on 0.5.0 with updates from the master branch) and features full support of NDNLPv2, including support for network NACKs. For more details about the release, refer to https://ndnsim.net/2.3/RELEASE_NOTES.html * We released version 0.3.1 of Named-data Link State Routing Protocol (NLSR). More information about NLSR, release notes, tutorials, installation and configuration guides, and other useful information can be found at: http://named-data.net/doc/NLSR/0.3.1/ NDN PUBLICATIONS, PRESENTATIONS, and TECHNICAL REPORTS * Wentao Shang, Alexander Afanasyev, and Lixia Zhang, "The Design and Implementation of the NDN Protocol Stack for RIOT-OS" published in the proceedings of GLOBECOM Workshop on Information Centric Networking Solutions for Real World Applications, December 2016 https://named-data.net/publications/design_implementation_ndn_protocol/ SEMINARS * The NDN seminars are internally focused. If you would like to participate in the NDN Seminars, please contact the PoC, UCLA PhD. candidate Spyridon Mastorakis for the most up-to-date information regarding upcoming seminars. - 14 December 2016 Wentao Shang, (University of California, Los Angeles) "VectorSync design overview" - 12 January 2016 Junxiao Shi (University of Arizona) "Technical Discussion of Self-Learning Strategy - 2 February 2017 2pm Jongdeog Lee (University of Illinois, Urbana-Champagne) "SwiftNDN: NDN support for iOS" For more information about the Named Data Networking (NDN) Project please visit http://www.named-data.net/. From mobinranjbar at hotmail.com Thu Feb 2 11:11:07 2017 From: mobinranjbar at hotmail.com (Mobin Ranjbar) Date: Thu, 2 Feb 2017 19:11:07 +0000 Subject: [Ndn-interest] Problem related to ndnSIM with Redis integration in Content-Store Message-ID: Hi there, I am going to replace Table data structure with Redis in-memory database in Content-Store for benchmarking purpose. I have downloaded a C++ client for Redis called Redox that has some .h and .hpp files. I have added #include parts in cs-entry.cpp and run ./waf. But there are some errors following below: ./libns3-dev-ndnSIM-debug.so: undefined reference to `ev_io_start` ./libns3-dev-ndnSIM-debug.so: undefined reference to `redisAsyncHandleRead` ./libns3-dev-ndnSIM-debug.so: undefined reference to `ev_io_stop` ./libns3-dev-ndnSIM-debug.so: undefined reference to `redisAsyncHandleWrite` ` I figured out that it does not find those headers but I do not know where do I have to put header definition to make './waf' aware of new module. Any idea about this problem? Where should .h and .hpp files be defined? I have defined them in ndn-all.hpp but no hopes. Thanks for your help. ________ Mobin Ranjbar Software Engineer, Big Data Evangelist and Startup Guy Co-Founder of Iran Startups Founder of Shariksho Editor in Chief at Techly.co Founder of FaraFekr Technology Founder of Hadoop.ir Founder of Big Data Watcher Website | Twitter | Linkedin | skype: mobinranjbar -------------- next part -------------- An HTML attachment was scrubbed... URL: From lanwang at memphis.edu Fri Feb 3 11:42:18 2017 From: lanwang at memphis.edu (Lan Wang (lanwang)) Date: Fri, 3 Feb 2017 19:42:18 +0000 Subject: [Ndn-interest] Named Data Networking Community Meeting (NDNcomm) 2017 (Deadline extended to 2/10/17) Message-ID: <90B520FD-7BB0-4C7F-84CE-00382D6647DD@memphis.edu> Call for Contributions Named Data Networking Community Meeting (NDNcomm) 2017 March 23-24, 2017 Memphis, TN, USA http://www.caida.org/workshops/ndn/1703/ Submission deadline: 23:59 EST, Friday, Feb. 10, 2017 The organizing committee invites you to contribute to NDNComm 2017 to be held at the University of Memphis, Memphis, TN, USA on March 23-24, 2017. NDNComm is an annual event that brings together a large community of researchers, users and other parties interested in Named Data Networking (NDN). NDN is an instance of Information Centric Networking (ICN), which allows named content to be accessed directly rather than through network hosts resulting in a network service model that is much better aligned with application requirements. Named content offers many advantages, such as reliability, security, scalability and robustness in communication. In addition, NDN is also highly suitable for newly emerging IoT applications. NDNcomm provides a community forum to discuss the state of the NDN software platform and testbed, and guide the evolution of the NDN architecture. As the NSF NDN-NP project concludes its final project year, NDNcomm 2017 will highlight the research results from this project team, in particular the IoT and multimedia applications developed by the project. Moreover, we invite submissions from the broader NDN community for presentations, posters, demos and panels on topics including but not limited to: ? NDN applications, such as scientific data, education, entertainment, tactical edge, smart cities and transportation; ? NDN support for IoT, mobile, and ad hoc environments; ? Security and privacy at different layers of the architecture; ? Management of NDN networks; ? Experience with NDN experimentation; ? Strategies to stimulate NDN development, both from research and commercial perspectives. Submission Instructions Submissions should be one page in PDF format containing a title, authors and an abstract. The title should start with ?Presentation:?, ?Poster:?, ?Demo:? or ?Panel:?. Please submit your abstract using http://ndncomm2017.named-data.net/. Deadlines ? Abstracts for presentations, posters, demos and panels: 23:59 EST, Friday, Feb. 10, 2017 ? Notifications: 23:59 EST, Friday, Feb. 24, 2017 Abstract submission is not required for attending NDNcomm 2017. Interested parties can register for NDNcomm 2017 at http://www.caida.org/workshops/ndn/1703/register.xml and the 4th NDN hackathon on March 25-26, 2017 at http://4th-ndn-hackathon.named-data.net. The community meeting will be webcast. Please visit the NDN website (www.named-data.net) closer to the meeting for instructions. Lan ************************************************ Lan Wang Professor & Chair Department of Computer Science University of Memphis Memphis, TN 38152 Phone: 901-678-1643 URL: http://www.cs.memphis.edu/~lanwang *********************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From jlee700 at illinois.edu Wed Feb 8 09:24:05 2017 From: jlee700 at illinois.edu (Lee, Jongdeog) Date: Wed, 8 Feb 2017 17:24:05 +0000 Subject: [Ndn-interest] Producing new contents with same name Message-ID: Dear all, I have questions regarding producing new contents with the same name. Sorry if they are duplicate questions. Suppose that my consumer always wants to fetch 'fresh' data from a producer (the interest should not hit the caches of intermediate routers). Also, the consumer wants to use the same name to do so. 1. Is it allowed to produce different contents with same name? 2. If it is allowed, what would be a conventional way to implement it? My thoughts are: - the interest of the consumer 'must be fresh' - the producer produces the contents with the minimal freshness period (0 or 1). 3. If there is any other conventional way of fetching the newest version of contents, please let me know. As we discussed in the NDN seminar, the selector (right most child) does not solve the problem as it can sometimes retrieve old cached data. Best wishes, Jongdeog Lee (JD) ------------------------------------------------ Ph.D. Student Department of Computer Science University of Illinois at Urbana-Champaign -------------- next part -------------- An HTML attachment was scrubbed... URL: From shijunxiao at email.arizona.edu Wed Feb 8 10:51:05 2017 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Wed, 8 Feb 2017 11:51:05 -0700 Subject: [Ndn-interest] Producing new contents with same name In-Reply-To: References: Message-ID: Hi Jongdeog 1. Is it allowed to produce different contents with same name? > No, it violates data immutability as required by NDN protocol design principles . 2. If it is allowed, what would be a conventional way to implement it? My > thoughts are: > - the interest of the consumer 'must be fresh' > - the producer produces the contents with the minimal freshness period (0 > or 1). > > 3. If there is any other conventional way of fetching the newest version > of contents, please let me know. As we discussed in the NDN seminar, the > selector (right most child) does not solve the problem as it can sometimes > retrieve old cached data. > You may use iterative version discovery : use ChildSelector=rightmost to find a version, then express another Interest that excludes that and all lower versions, repeat until you are unable to retrieval any newer versions. A drawback is that there needs to be a timeout to complete this version discovery procedure. So far, no valid alternative solution has been proposed. You may post your idea in #3793. Yours, Junxiao -------------- next part -------------- An HTML attachment was scrubbed... URL: From jlee700 at illinois.edu Wed Feb 8 11:56:27 2017 From: jlee700 at illinois.edu (Lee, Jongdeog) Date: Wed, 8 Feb 2017 19:56:27 +0000 Subject: [Ndn-interest] Producing new contents with same name In-Reply-To: References: , Message-ID: Dear Junxiao, Thanks for your reply. I would like to use sync variable (unix timestamp) for my application with assuming loosely synchronized clocks between producer and consumer. Best wishes, Jongdeog Lee (JD) ------------------------------------------------ Ph.D. Student Department of Computer Science University of Illinois at Urbana-Champaign ________________________________ From: Junxiao Shi [shijunxiao at email.arizona.edu] Sent: Wednesday, February 08, 2017 12:51 PM To: Lee, Jongdeog Cc: ndn-interest at lists.cs.ucla.edu Subject: Re: [Ndn-interest] Producing new contents with same name Hi Jongdeog 1. Is it allowed to produce different contents with same name? No, it violates data immutability as required by NDN protocol design principles. 2. If it is allowed, what would be a conventional way to implement it? My thoughts are: - the interest of the consumer 'must be fresh' - the producer produces the contents with the minimal freshness period (0 or 1). 3. If there is any other conventional way of fetching the newest version of contents, please let me know. As we discussed in the NDN seminar, the selector (right most child) does not solve the problem as it can sometimes retrieve old cached data. You may use iterative version discovery: use ChildSelector=rightmost to find a version, then express another Interest that excludes that and all lower versions, repeat until you are unable to retrieval any newer versions. A drawback is that there needs to be a timeout to complete this version discovery procedure. So far, no valid alternative solution has been proposed. You may post your idea in #3793. Yours, Junxiao -------------- next part -------------- An HTML attachment was scrubbed... URL: From lixia at CS.UCLA.EDU Wed Feb 8 16:58:22 2017 From: lixia at CS.UCLA.EDU (Lixia Zhang) Date: Wed, 8 Feb 2017 16:58:22 -0800 Subject: [Ndn-interest] Producing new contents with same name In-Reply-To: References: Message-ID: <0E939732-473A-4161-80EF-4EC808661D0D@cs.ucla.edu> > On Feb 8, 2017, at 10:51 AM, Junxiao Shi wrote: > > Hi Jongdeog > > 1. Is it allowed to produce different contents with same name? > No, it violates data immutability as required by NDN protocol design principles . > > 2. If it is allowed, what would be a conventional way to implement it? My thoughts are: > - the interest of the consumer 'must be fresh' > - the producer produces the contents with the minimal freshness period (0 or 1). > > 3. If there is any other conventional way of fetching the newest version of contents, please let me know. As we discussed in the NDN seminar, the selector (right most child) does not solve the problem as it can sometimes retrieve old cached data. > You may use iterative version discovery : use ChildSelector=rightmost to find a version, then express another Interest that excludes that and all lower versions, repeat until you are unable to retrieval any newer versions. A drawback is that there needs to be a timeout to complete this version discovery procedure. > So far, no valid alternative solution has been proposed. I would like to express a different view from Junxiao?s last statement above. 1/ regarding requesting data with the same "name": I would like to draw people?s attention to the important distinction between an exact name and a name prefix. One must not put different contents under the same exact name. one can use the same name prefix to fetch future content under that name prefix. 2/ as Jongdeog?s earlier msg already mentioned, he thought about using a combination of "must be fresh" flag on an Interest packet and "FreshnessPeriod" to achieve the goal of fetching latest content: a) the producer sets "FreshnessPeriod" in its data packet to a small value. b) a consumer sets "must be fresh" flag its Interest packet c) This will prevent intermediate forwarders from replying to the Interest with Data packet whose "FreshnessPeriod" already expired, so that the Interest will be forwarded toward the producer. d) I would also like to make it clear that the "FreshnessPeriod" is a relative time, it gets restarted at each hop. Therefore it is not an upper bound of "freshness" as measured by how long the data packet has left the original producer. Nevertheless it is an effective measure for the producer to control how frequently it can handle incoming Interests for its latest content. Lixia -------------- next part -------------- An HTML attachment was scrubbed... URL: From Matteo.Bertolino at eurecom.fr Thu Feb 9 06:40:27 2017 From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino) Date: Thu, 09 Feb 2017 15:40:27 +0100 Subject: [Ndn-interest] Adding a new type of NACK Message-ID: <20170209154027.tvjeqwelkwog4kws@webmail.eurecom.fr> Good morning, I am trying to add a new type of NACK called "PERSONALIZED" in ndn-cxx. Then I modify the strategy method "after receive NACK" with: if (nack.getReason() == lp::NackReason::PERSONALIZED) { log << "I received a PERSONALIZED NACK"; } But when I compile I have the error: "PERSONALIZED" is not a member of "ndn::lp::NackReason". My steps to add the new NACK were: 1) modifying ndn-cxx/src/lp/nack-header.cpp adding: case NackReason::PERSONALIZED: os << "MyPersonalNACK"; break; in the method operator << 2) adding the equivalent in the method getReason() always in nack-header.cpp 3) in nack-header.hpp I add: enum class NackReason { NONE = 0; CONGESTION = 50; ... PERSONALIZED = 200; } What did I forgot ? Thanks in advance Bests, Matteo ------------------------------------------------------------------------------- This message was sent using EURECOM Webmail: http://webmail.eurecom.fr From lixia at CS.UCLA.EDU Thu Feb 9 09:06:48 2017 From: lixia at CS.UCLA.EDU (Lixia Zhang) Date: Thu, 9 Feb 2017 09:06:48 -0800 Subject: [Ndn-interest] Adding a new type of NACK In-Reply-To: <20170209154027.tvjeqwelkwog4kws@webmail.eurecom.fr> References: <20170209154027.tvjeqwelkwog4kws@webmail.eurecom.fr> Message-ID: just a note to let people know: I redirected the question below to nfd-dev mailing list and the issue has been resolved. nfd-dev list is not limited to nfd issues but is for all development related questions (we should have called it ndn-dev list:) Lixia > On Feb 9, 2017, at 6:40 AM, Matteo Bertolino wrote: > > Good morning, > I am trying to add a new type of NACK called "PERSONALIZED" in ndn-cxx. > Then I modify the strategy method "after receive NACK" with: > if (nack.getReason() == lp::NackReason::PERSONALIZED) { > log << "I received a PERSONALIZED NACK"; > } > > But when I compile I have the error: > "PERSONALIZED" is not a member of "ndn::lp::NackReason". > > > My steps to add the new NACK were: > 1) modifying ndn-cxx/src/lp/nack-header.cpp > > adding: > case NackReason::PERSONALIZED: > os << "MyPersonalNACK"; > break; > > in the method operator << > > 2) adding the equivalent in the method getReason() always in nack-header.cpp > > 3) in nack-header.hpp I add: > enum class NackReason { > NONE = 0; > CONGESTION = 50; > ... > PERSONALIZED = 200; > } > > What did I forgot ? > > Thanks in advance > Bests, > Matteo > > ------------------------------------------------------------------------------- > This message was sent using EURECOM Webmail: http://webmail.eurecom.fr > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest From Matteo.Bertolino at eurecom.fr Fri Feb 10 10:18:08 2017 From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino) Date: Fri, 10 Feb 2017 19:18:08 +0100 Subject: [Ndn-interest] How to send a signed interest in ndn-js? Message-ID: <20170210191808.m05pbuleokgo48s8@webmail.eurecom.fr> Good morning all, I wrote: var k = new KeyChain(); k.prototype.sign(interest, '/root/site1'); or k.prototype.signWithSha256(interest'); But... nothing happens. Any idea ? ------------------------------------------------------------------------------- This message was sent using EURECOM Webmail: http://webmail.eurecom.fr From jefft0 at remap.ucla.edu Fri Feb 10 10:42:21 2017 From: jefft0 at remap.ucla.edu (Thompson, Jeff) Date: Fri, 10 Feb 2017 18:42:21 +0000 Subject: [Ndn-interest] How to send a signed interest in ndn-js? In-Reply-To: <20170210191808.m05pbuleokgo48s8@webmail.eurecom.fr> References: <20170210191808.m05pbuleokgo48s8@webmail.eurecom.fr> Message-ID: Hi Matteo, Usually the reason to sign an interest is to make a command interest. Have you looked at the example? https://github.com/named-data/ndn-js/blob/master/examples/node/test-encode-decode-interest.js#L231 Here?s the API for makeCommandInterest: http://named-data.net/doc/ndn-ccl-api/face.html#face-makecommandinterest-method Thanks, - Jeff T On 2017/2/10, 10:18:08, "Ndn-interest on behalf of Matteo Bertolino" on behalf of Matteo.Bertolino at eurecom.fr> wrote: Good morning all, I wrote: var k = new KeyChain(); k.prototype.sign(interest, '/root/site1'); or k.prototype.signWithSha256(interest'); But... nothing happens. Any idea ? ------------------------------------------------------------------------------- This message was sent using EURECOM Webmail: http://webmail.eurecom.fr _______________________________________________ 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 Matteo.Bertolino at eurecom.fr Fri Feb 10 11:01:50 2017 From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino) Date: Fri, 10 Feb 2017 20:01:50 +0100 Subject: [Ndn-interest] How to send a signed interest in ndn-js? Message-ID: <20170210200150.svyz5uflqyo488w@webmail.eurecom.fr> Dear Jeff Thompson, thank you for the reply. I tried, but the syntax is incredible complex ant I had no success. In c++, I simply write: Name consumerId("/root/site2"); m_keyChain.signByIdentity(interest, consumerId); m_face->expressInterest(interest, //callbacks) 3 lines :) Is not something of similar in js? I had not understand that example unfortunately.. Bests, Matteo Quoting "Thompson, Jeff" : > Hi Matteo, > > Usually the reason to sign an interest is to make a command > interest. Have you looked at the example? > https://github.com/named-data/ndn-js/blob/master/examples/node/test-encode-decode-interest.js#L231 > > Here?s the API for makeCommandInterest: > http://named-data.net/doc/ndn-ccl-api/face.html#face-makecommandinterest-method > > Thanks, > - Jeff T > > On 2017/2/10, 10:18:08, "Ndn-interest on behalf of Matteo Bertolino" > > on behalf of Matteo.Bertolino at eurecom.fr> > wrote: > > Good morning all, > I wrote: > > var k = new KeyChain(); > k.prototype.sign(interest, '/root/site1'); > or > k.prototype.signWithSha256(interest'); > > But... nothing happens. > > Any idea ? > > ------------------------------------------------------------------------------- > This message was sent using EURECOM Webmail: http://webmail.eurecom.fr > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > ------------------------------------------------------------------------------- This message was sent using EURECOM Webmail: http://webmail.eurecom.fr ----- End forwarded message ----- ------------------------------------------------------------------------------- This message was sent using EURECOM Webmail: http://webmail.eurecom.fr From lanwang at memphis.edu Fri Feb 10 12:15:36 2017 From: lanwang at memphis.edu (Lan Wang (lanwang)) Date: Fri, 10 Feb 2017 20:15:36 +0000 Subject: [Ndn-interest] Named Data Networking Community Meeting (NDNcomm) 2017 (Deadline extended to 2/10/17) Message-ID: <18F2C7D6-266B-429C-8A9F-C74A2FAF6A49@memphis.edu> Call for Contributions Named Data Networking Community Meeting (NDNcomm) 2017 March 23-24, 2017 Memphis, TN, USA http://www.caida.org/workshops/ndn/1703/ Submission deadline: 23:59 EST, Friday, Feb. 10, 2017 The organizing committee invites you to contribute to NDNComm 2017 to be held at the University of Memphis, Memphis, TN, USA on March 23-24, 2017. NDNComm is an annual event that brings together a large community of researchers, users and other parties interested in Named Data Networking (NDN). NDN is an instance of Information Centric Networking (ICN), which allows named content to be accessed directly rather than through network hosts resulting in a network service model that is much better aligned with application requirements. Named content offers many advantages, such as reliability, security, scalability and robustness in communication. In addition, NDN is also highly suitable for newly emerging IoT applications. NDNcomm provides a community forum to discuss the state of the NDN software platform and testbed, and guide the evolution of the NDN architecture. As the NSF NDN-NP project concludes its final project year, NDNcomm 2017 will highlight the research results from this project team, in particular the IoT and multimedia applications developed by the project. Moreover, we invite submissions from the broader NDN community for presentations, posters, demos and panels on topics including but not limited to: ? NDN applications, such as scientific data, education, entertainment, tactical edge, smart cities and transportation; ? NDN support for IoT, mobile, and ad hoc environments; ? Security and privacy at different layers of the architecture; ? Management of NDN networks; ? Experience with NDN experimentation; ? Strategies to stimulate NDN development, both from research and commercial perspectives. Submission Instructions Submissions should be one page in PDF format containing a title, authors and an abstract. The title should start with ?Presentation:?, ?Poster:?, ?Demo:? or ?Panel:?. Please submit your abstract using http://ndncomm2017.named-data.net/. Deadlines ? Abstracts for presentations, posters, demos and panels: 23:59 EST, Friday, Feb. 10, 2017 ? Notifications: 23:59 EST, Friday, Feb. 24, 2017 Abstract submission is not required for attending NDNcomm 2017. Interested parties can register for NDNcomm 2017 at http://www.caida.org/workshops/ndn/1703/register.xml and the 4th NDN hackathon on March 25-26, 2017 at http://4th-ndn-hackathon.named-data.net. The community meeting will be webcast. Please visit the NDN website (www.named-data.net) closer to the meeting for instructions. Lan ************************************************ Lan Wang Professor & Chair Department of Computer Science University of Memphis Memphis, TN 38152 Phone: 901-678-1643 URL: http://www.cs.memphis.edu/~lanwang *********************************************** Lan -------------- next part -------------- An HTML attachment was scrubbed... URL: From anilj.mailing at gmail.com Sat Feb 11 09:32:18 2017 From: anilj.mailing at gmail.com (Anil Jangam) Date: Sat, 11 Feb 2017 09:32:18 -0800 Subject: [Ndn-interest] =?utf-8?q?Cisco_VNI_Global_Mobile_Data_Forecast=2C?= =?utf-8?b?IDIwMTbigJMyMDIxLg==?= Message-ID: If you haven't seen this so far. http://www.cisco.com/c/en/us/solutions/collateral/service-provider/visual-networking-index-vni/mobile-white-paper-c11-520862.html /anil. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at CS.UCLA.EDU Fri Feb 17 17:57:16 2017 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Fri, 17 Feb 2017 17:57:16 -0800 (PST) Subject: [Ndn-interest] [CFP] ACM ICN 2017 - Poster and Demos Message-ID: <58a7a9fc.d1a6620a.4a243.2930@mx.google.com> ACM ICN 2017 - CALL FOR POSTERS AND DEMOS 4th ACM Conference on Information-Centric Networking Berlin, Germany on Sep. 26-28, 2017 http://conferences2.sigcomm.org/acm-icn/2017/cf-posters-and-demos.html ========================================================= The ICN poster and demo sessions are intended to showcase works-in-progress. Topics of interest are the same as those listed in the main track call for papers. We strongly encourage both student and industry submissions. Both demos and posters should be accompanied by a two-page extended abstract, which will be published in the conference proceedings. We specifically encourage submissions of posters and demos that are accompanied with datasets. Such submissions will have a preferential treatment during the review and will be eligible for special awards. The aim is to collect and share datasets that can hopefully become a common ground for evaluation in the ICN community. The posters and demos submitted to ACM ICN 2017 must be original and cannot be concurrently submitted to other workshops or conferences during the ACM ICN 2017 poster/demo review period. All dual submissions will be rejected without review. WHY SHOULD YOU SUBMIT A POSTER OR A DEMO? Presenting a poster is a great opportunity, especially for students, to obtain interesting and valuable feedback on ongoing research from a knowledgeable crowd at the conference. Accepted posters and demos will be published as a two-page abstract for the archived conference proceedings. Students who are submitting posters are highly encouraged to examine if they are eligible for student travel grants. MORE DETAILS http://conferences2.sigcomm.org/acm-icn/2017/cf-posters-and-demos.html ========================================================= IMPORTANT DATES Submission Deadline: July 9, 2017 12am EDT Acceptance Notification: March 1, 2017 Camera Ready Due: August 21, 2017 ========================================================= From lpi at memphis.edu Tue Feb 21 10:55:53 2017 From: lpi at memphis.edu (Lei Pi) Date: Tue, 21 Feb 2017 12:55:53 -0600 Subject: [Ndn-interest] [Question] What's the purpose of the NFD's default signing key? Message-ID: Hi, While ?reading documents on redmine, I found myself confused ? with? ? ? ? ? the "*Using registerPrefix with NFD*" part of article "*Application Development Documentation / Guides*"[1]. ? ? The original text of the article goes as follows: >>> When you install NFD, it installs a default signing key on your system. For registerPrefix to create a signed command interest using this default signing key, your application needs to use the default KeyChain constructor and call setCommandSigningInfo so that the Face can sign the command interest created by registerPrefix ?But ? ? when an application sends out a command interest, the recipient ?should check if the interest's signing key is finally signed by an ?administrator's signing key in order to reject unauthorized commands ?.? So what's the purpose of the NFD's default signing key? Why should the app use this key ? to initialize its identity? ? Note the NFD's default signing key is not signed by anyone ?[2].? If it is also ? for defend ?ing? against unauthorized command interests, then any local app, including possible malwares, can also use this key to sign their interest by simply using the default keychain. If not, what other purpose could it be? ?[1] https://redmine.named-data.net/projects/application- development-documentation-guides/wiki/Using_Client_ Libraries_with_NDNx_vs_NDNx-TLV_vs_NFD#Using-registerPrefix-with-NFD ?[2] https://github.com/named-data/NFD/blob/master/tools/nfd-start.sh#L42 ? ? Thank you. ? -- Regards, Lei ?Pi University of Memphis? -------------- next part -------------- An HTML attachment was scrubbed... URL: From susmit at cs.colostate.edu Wed Feb 22 09:35:10 2017 From: susmit at cs.colostate.edu (Susmit) Date: Wed, 22 Feb 2017 10:35:10 -0700 Subject: [Ndn-interest] 4th NDN Hackathon - Call for Hacks In-Reply-To: References: Message-ID: Hi All, This is a gentle reminder that the Hackathon project proposals are due by next Wednesday, March 1st. Thanks. On Mon, Jan 9, 2017 at 3:51 PM, Susmit wrote: > ====================================== > CALL FOR HACKS > The 4th Named Data Networking (NDN) Hackathon > University of Memphis, TN > ====================================== > > ------------------------------------------ > IMPORTANT DATES > ------------------------------------------ > Submission deadline: March 1, 2017 > Acceptance notification: March 7, 2017 > > Team Formation: March 24th, 2017 > Hackathon: March 25th, 26th, 2017 > > ------------------------------------------ > WEBSITE AND PROGRAM > ------------------------------------------ > http://4th-ndn-hackathon.named-data.net > http://4th-ndn-hackathon.named-data.net/program.html > > ------------------------------------------ > REGISTRATION LINK > ------------------------------------------ > https://www.eventbrite.com/e/4th-ndn-hackathon-tickets-29700938306 > > ------------------------------------------ > CALL FOR HACKS > ------------------------------------------ > > The NDN team is organizing the 4th NDN Hackathon on March 25th and > March 26th at University of Memphis, TN. > We solicit hackathon proposals that advance the state of NDN. > Participants will have approximately **12 hours** to work on their > projects. > > We encourage projects that: > > - directly address NDN research needs, > - create new NDN tools or modify existing tools, > - create or improve documentation and how-to guides. > > ------------------------------------------ > SUBMISSION GUIDELINES > ------------------------------------------ > > Proposals should be submitted via email to <4th-ndn-hackathon at named-data.net>. > > The submissions should include: > > - 1 page description PDF that includes the following: > -- Contact information of submitter > -- Problem statement > -- Planned tasks to accomplish > -- Knowledge requirements, and > -- Expected outcome by the end of the hackathon. > > - 1 PPTx/PDF slide, listing the project leader(s) and summarizing the > problem, contribution, tasks, required knowledge, and expected outcome. > > All submitted proposals will be reviewed by the hacking Committee. > > If accepted, the project leader is expected to give a 5 minute ?pitch? > presentation at the beginning of the Hackathon, soliciting participation > from attendees. > > We hope that this hackathon will be a fun event for everyone and that projects > will lead to collaborations extending beyond the hackathon. > > We look forward to your participation in the hackathon. -- Regards, Susmit ==================================== http://www.cs.colostate.edu/~susmit ==================================== From lanwang at memphis.edu Wed Feb 22 19:59:36 2017 From: lanwang at memphis.edu (Lan Wang (lanwang)) Date: Thu, 23 Feb 2017 03:59:36 +0000 Subject: [Ndn-interest] [Question] What's the purpose of the NFD's default signing key? In-Reply-To: References: Message-ID: <957E3C64-5334-425D-A01F-462360F41C62@memphis.edu> Lei, Alex would be a better person to explain this. My questions about your questions below: On Feb 21, 2017, at 12:55 PM, Lei Pi > wrote: Hi, While ?reading documents on redmine, I found myself confused ? with? ? ? ? ? the "Using registerPrefix with NFD" part of article "Application Development Documentation / Guides"[1]. ? ? The original text of the article goes as follows: >>> When you install NFD, it installs a default signing key on your system. For registerPrefix to create a signed command interest using this default signing key, your application needs to use the default KeyChain constructor and call setCommandSigningInfo so that the Face can sign the command interest created by registerPrefix ?But ? ? when an application sends out a command interest, the recipient ?should check if the interest's signing key is finally signed by an ?administrator's signing key in order to reject unauthorized commands ?.? How do you know "the recipient ?should check if the interest's signing key is finally signed by an ?administrator's signing key in order to reject unauthorized commands ?.??? What checking is needed depends on the trust model. What?s the trust model here? So what's the purpose of the NFD's default signing key? Why should the app use this key ? to initialize its identity? ? Note the NFD's default signing key is not signed by anyone ?[2].? The line you are referring to doesn?t seem to be relevant to "the NFD's default signing key is not signed by anyone ??. If it is also ? for defend ?ing? against unauthorized command interests, then any local app, including possible malwares, can also use this key to sign their interest by simply using the default keychain. The assumption is that local apps are trusted if they are allowed to run. There needs to be checking before they are launched. The secure launcher part is not implemented (or designed) yet. Lan If not, what other purpose could it be? ?[1] https://redmine.named-data.net/projects/application-development-documentation-guides/wiki/Using_Client_Libraries_with_NDNx_vs_NDNx-TLV_vs_NFD#Using-registerPrefix-with-NFD ?[2] https://github.com/named-data/NFD/blob/master/tools/nfd-start.sh#L42 ? ? Thank you. ? -- Regards, Lei ?Pi University of Memphis? _______________________________________________ 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 lpi at memphis.edu Wed Feb 22 20:02:48 2017 From: lpi at memphis.edu (Lei Pi (lpi)) Date: Thu, 23 Feb 2017 04:02:48 +0000 Subject: [Ndn-interest] Questions about ndn porting to golang Message-ID: <857223EE-E5A2-4CA3-8FFD-635D5F2DD1F1@memphis.edu> Hi everyone, While thinking about proposals for the coming NDN Hackathon, I?m curious about the possibilities to write NDN applications in golang. There is a go-ndn project on github [1], which seems to be re-implementing ndn in golang. But it is not officially supported or maintained. Another option for using ndn in golang is to link the binary with the libndncxx / libndncpp library. [2][3][4] Does anyone already have experience in using SWIG to link golang programs with libndncxx or libndncpp? [1] https://github.com/go-ndn/ndn [2] https://golang.org/doc/faq#Do_Go_programs_link_with_Cpp_programs [3] https://golang.org/cmd/cgo/ [4] http://www.swig.org/Doc3.0/Go.html Thank you. ---- Regards, Lei Pi University of Memphis Masters Student in Computer Science -------------- next part -------------- An HTML attachment was scrubbed... URL: From lpi at memphis.edu Wed Feb 22 20:53:38 2017 From: lpi at memphis.edu (Lei Pi (lpi)) Date: Thu, 23 Feb 2017 04:53:38 +0000 Subject: [Ndn-interest] [Question] What's the purpose of the NFD's default signing key? In-Reply-To: <957E3C64-5334-425D-A01F-462360F41C62@memphis.edu> References: <957E3C64-5334-425D-A01F-462360F41C62@memphis.edu> Message-ID: <450F553A-2353-452A-9335-B42D9F8C2007@memphis.edu> Hi Dr. Wang, How do you know "the recipient ?should check if the interest's signing key is finally signed by an ?administrator's signing key in order to reject unauthorized commands ?.??? What checking is needed depends on the trust model. What?s the trust model here? Under specific scenarios whether the recipient should do the checking is up to the designer?s decision. I?m possibly wrong, but NFD is making decision for the recipients about which signing key the command interest is signed with should be trusted. Why isn?t that limiting the possibilities of designs? And why is that necessary? So what's the purpose of the NFD's default signing key? Why should the app use this key ? to initialize its identity? ? Note the NFD's default signing key is not signed by anyone ?[2].? The line you are referring to doesn?t seem to be relevant to "the NFD's default signing key is not signed by anyone ??. The line is generating a new key and that key looks like a self-signed key or unsigned key. I believe this is what the article I was citing means. My question about this is in the next line. If it is also ? for defend ?ing? against unauthorized command interests, then any local app, including possible malwares, can also use this key to sign their interest by simply using the default keychain. The assumption is that local apps are trusted if they are allowed to run. There needs to be checking before they are launched. The secure launcher part is not implemented (or designed) yet. Then is it right to say that unless the secure launcher is a fully automatic one which makes no mistakes, the user will be involved in deciding trusted apps instead of the protocol or the service providers? I understand now it can be used to by default deny forwarding all remote command interests. Thank you. Lan If not, what other purpose could it be? ?[1] https://redmine.named-data.net/projects/application-development-documentation-guides/wiki/Using_Client_Libraries_with_NDNx_vs_NDNx-TLV_vs_NFD#Using-registerPrefix-with-NFD ?[2] https://github.com/named-data/NFD/blob/master/tools/nfd-start.sh#L42 ? ? Thank you. ? -- Regards, Lei ?Pi University of Memphis? _______________________________________________ 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 Wed Feb 22 21:09:41 2017 From: lanwang at memphis.edu (Lan Wang (lanwang)) Date: Thu, 23 Feb 2017 05:09:41 +0000 Subject: [Ndn-interest] [Question] What's the purpose of the NFD's default signing key? In-Reply-To: <450F553A-2353-452A-9335-B42D9F8C2007@memphis.edu> References: <957E3C64-5334-425D-A01F-462360F41C62@memphis.edu> <450F553A-2353-452A-9335-B42D9F8C2007@memphis.edu> Message-ID: <299AAF88-66F8-4896-A38F-232EAA0C0A9E@memphis.edu> Lei, Just realized that the application development guide you are referring to was written in 2014 by Jeff Thompson and it is for NDN-CCL. I suggest confirming with Jeff that this is up to date and if so clarify your questions with him first. Lan On Feb 22, 2017, at 10:53 PM, Lei Pi (lpi) > wrote: Hi Dr. Wang, How do you know "the recipient ?should check if the interest's signing key is finally signed by an ?administrator's signing key in order to reject unauthorized commands ?.??? What checking is needed depends on the trust model. What?s the trust model here? Under specific scenarios whether the recipient should do the checking is up to the designer?s decision. I?m possibly wrong, but NFD is making decision for the recipients about which signing key the command interest is signed with should be trusted. Why isn?t that limiting the possibilities of designs? And why is that necessary? So what's the purpose of the NFD's default signing key? Why should the app use this key ? to initialize its identity? ? Note the NFD's default signing key is not signed by anyone ?[2].? The line you are referring to doesn?t seem to be relevant to "the NFD's default signing key is not signed by anyone ??. The line is generating a new key and that key looks like a self-signed key or unsigned key. I believe this is what the article I was citing means. My question about this is in the next line. If it is also ? for defend ?ing? against unauthorized command interests, then any local app, including possible malwares, can also use this key to sign their interest by simply using the default keychain. The assumption is that local apps are trusted if they are allowed to run. There needs to be checking before they are launched. The secure launcher part is not implemented (or designed) yet. Then is it right to say that unless the secure launcher is a fully automatic one which makes no mistakes, the user will be involved in deciding trusted apps instead of the protocol or the service providers? I understand now it can be used to by default deny forwarding all remote command interests. Thank you. Lan If not, what other purpose could it be? ?[1] https://redmine.named-data.net/projects/application-development-documentation-guides/wiki/Using_Client_Libraries_with_NDNx_vs_NDNx-TLV_vs_NFD#Using-registerPrefix-with-NFD ?[2] https://github.com/named-data/NFD/blob/master/tools/nfd-start.sh#L42 ? ? Thank you. ? -- Regards, Lei ?Pi University of Memphis? _______________________________________________ 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 lpi at memphis.edu Wed Feb 22 21:11:37 2017 From: lpi at memphis.edu (Lei Pi (lpi)) Date: Thu, 23 Feb 2017 05:11:37 +0000 Subject: [Ndn-interest] [Question] What's the purpose of the NFD's default signing key? In-Reply-To: <299AAF88-66F8-4896-A38F-232EAA0C0A9E@memphis.edu> References: <957E3C64-5334-425D-A01F-462360F41C62@memphis.edu> <450F553A-2353-452A-9335-B42D9F8C2007@memphis.edu> <299AAF88-66F8-4896-A38F-232EAA0C0A9E@memphis.edu> Message-ID: <3264deb4-290b-4dd9-937c-f3b1c843c63f@Spark> Thank you. ---- Regards, Lei On Feb 22, 2017, 11:09 PM -0600, Lan Wang (lanwang) , wrote: Lei, Just realized that the application development guide you are referring to was written in 2014 by Jeff Thompson and it is for NDN-CCL. I suggest confirming with Jeff that this is up to date and if so clarify your questions with him first. Lan On Feb 22, 2017, at 10:53 PM, Lei Pi (lpi) > wrote: Hi Dr. Wang, How do you know "the recipient ?should check if the interest's signing key is finally signed by an ?administrator's signing key in order to reject unauthorized commands ?.??? What checking is needed depends on the trust model. What?s the trust model here? Under specific scenarios whether the recipient should do the checking is up to the designer?s decision. I?m possibly wrong, but NFD is making decision for the recipients about which signing key the command interest is signed with should be trusted. Why isn?t that limiting the possibilities of designs? And why is that necessary? So what's the purpose of the NFD's default signing key? Why should the app use this key ? to initialize its identity? ? Note the NFD's default signing key is not signed by anyone ?[2].? The line you are referring to doesn?t seem to be relevant to "the NFD's default signing key is not signed by anyone ??. The line is generating a new key and that key looks like a self-signed key or unsigned key. I believe this is what the article I was citing means. My question about this is in the next line. If it is also ? for defend ?ing? against unauthorized command interests, then any local app, including possible malwares, can also use this key to sign their interest by simply using the default keychain. The assumption is that local apps are trusted if they are allowed to run. There needs to be checking before they are launched. The secure launcher part is not implemented (or designed) yet. Then is it right to say that unless the secure launcher is a fully automatic one which makes no mistakes, the user will be involved in deciding trusted apps instead of the protocol or the service providers? I understand now it can be used to by default deny forwarding all remote command interests. Thank you. Lan If not, what other purpose could it be? ?[1] https://redmine.named-data.net/projects/application-development-documentation-guides/wiki/Using_Client_Libraries_with_NDNx_vs_NDNx-TLV_vs_NFD#Using-registerPrefix-with-NFD ?[2] https://github.com/named-data/NFD/blob/master/tools/nfd-start.sh#L42 ? ? Thank you. ? -- Regards, Lei ?Pi University of Memphis? _______________________________________________ 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 aa at CS.UCLA.EDU Wed Feb 22 21:22:44 2017 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Wed, 22 Feb 2017 21:22:44 -0800 Subject: [Ndn-interest] [Question] What's the purpose of the NFD's default signing key? In-Reply-To: References: Message-ID: <40644624-11D8-4D06-89D2-0E64E06A59CD@cs.ucla.edu> As Lan pointed out already, [1] is very old guide for NDNx codebase and many statements there don't apply to NFD. The "default" key that is created by nfd-start is only used to sign responses for NFD management requests and commands and current tools don't do validation of the responses. The applications and tools that want to register prefixes with NFD, they need to use keys that are authorized by NFD for this operation. In our default deployment, we have a very relaxed policy to allow any local registrations, which can be tied up in nfd.conf. The default policy for "remote" registration (using /localhop/nfd) is to deny all and on our testbed nodes we require commands to be signed by a valid NDN Testbed certificate. --- Alex > On Feb 21, 2017, at 10:55 AM, Lei Pi wrote: > > Hi, > > While ?reading documents on redmine, I found myself confused? with????? the "Using registerPrefix with NFD" part of article "Application Development Documentation / Guides"[1].? ?The original text of the article goes as follows: > > >>> When you install NFD, it installs a default signing key on your system. For registerPrefix to create a signed command interest using this default signing key, your application needs to use the default KeyChain constructor and call setCommandSigningInfo so that the Face can sign the command interest created by registerPrefix > > ?But? ?when an application sends out a command interest, the recipient ?should check if the interest's signing key is finally signed by an ?administrator's signing key in order to reject unauthorized commands?.? > > So what's the purpose of the NFD's default signing key? Why should the app use this key? to initialize its identity?? Note the NFD's default signing key is not signed by anyone?[2].? > > If it is also? for defend?ing? against unauthorized command interests, then any local app, including possible malwares, can also use this key to sign their interest by simply using the default keychain. > If not, what other purpose could it be? > > > ?[1] https://redmine.named-data.net/projects/application-development-documentation-guides/wiki/Using_Client_Libraries_with_NDNx_vs_NDNx-TLV_vs_NFD#Using-registerPrefix-with-NFD > ?[2] https://github.com/named-data/NFD/blob/master/tools/nfd-start.sh#L42 ? > > ? > > Thank you. ? > -- > Regards, > Lei ?Pi > University of Memphis? > _______________________________________________ > 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 aa at CS.UCLA.EDU Wed Feb 22 21:26:43 2017 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Wed, 22 Feb 2017 21:26:43 -0800 Subject: [Ndn-interest] Questions about ndn porting to golang In-Reply-To: <857223EE-E5A2-4CA3-8FFD-635D5F2DD1F1@memphis.edu> References: <857223EE-E5A2-4CA3-8FFD-635D5F2DD1F1@memphis.edu> Message-ID: <3E1550D3-2A55-4A86-8272-F7924DA6A534@cs.ucla.edu> I haven't worked with swig/go, but looked for it when some time ago regarding python bindings. I didn't find it to be very easy to write swig bindings and it looked a bit fragile and error-prone to use. For golang, I think using ndn-cxx library would defeat some of the advantages that golang provides, specifically the concurrency. But I agree, maintaining multiple libraries would be a lot of work. Though if there are users for the library, the users themselves can try to do such maintenance :-D -- Alex > On Feb 22, 2017, at 8:02 PM, Lei Pi (lpi) wrote: > > Hi everyone, > > While thinking about proposals for the coming NDN Hackathon, I?m curious about the possibilities to write NDN applications in golang. > > There is a go-ndn project on github [1], which seems to be re-implementing ndn in golang. But it is not officially supported or maintained. > > Another option for using ndn in golang is to link the binary with the libndncxx / libndncpp library. [2][3][4] > > Does anyone already have experience in using SWIG to link golang programs with libndncxx or libndncpp? > > [1] https://github.com/go-ndn/ndn > [2] https://golang.org/doc/faq#Do_Go_programs_link_with_Cpp_programs [3] https://golang.org/cmd/cgo/ > [4] http://www.swig.org/Doc3.0/Go.html > > Thank you. > ---- > Regards, > Lei Pi > University of Memphis > Masters Student in Computer Science -------------- next part -------------- An HTML attachment was scrubbed... URL: From lixia at CS.UCLA.EDU Wed Feb 22 21:28:04 2017 From: lixia at CS.UCLA.EDU (Lixia Zhang) Date: Wed, 22 Feb 2017 21:28:04 -0800 Subject: [Ndn-interest] [Question] What's the purpose of the NFD's default signing key? In-Reply-To: <40644624-11D8-4D06-89D2-0E64E06A59CD@cs.ucla.edu> References: <40644624-11D8-4D06-89D2-0E64E06A59CD@cs.ucla.edu> Message-ID: <2DB10E77-7C08-436F-BE50-76AB0BB54485@cs.ucla.edu> > On Feb 22, 2017, at 9:22 PM, Alex Afanasyev wrote: > > As Lan pointed out already, [1] is very old guide for NDNx codebase and many statements there don't apply to NFD. I guess new people like Lei has no clue what NDNx was:) wonder whether there is an easy way to mark those old/obsolete stuff to prevent future confusion. > The "default" key that is created by nfd-start is only used to sign responses for NFD management requests and commands and current tools don't do validation of the responses. The applications and tools that want to register prefixes with NFD, they need to use keys that are authorized by NFD for this operation. In our default deployment, we have a very relaxed policy to allow any local registrations, which can be tied up in nfd.conf. The default policy for "remote" registration (using /localhop/nfd) is to deny all and on our testbed nodes we require commands to be signed by a valid NDN Testbed certificate. > > --- > Alex > >> On Feb 21, 2017, at 10:55 AM, Lei Pi > wrote: >> >> Hi, >> >> While ?reading documents on redmine, I found myself confused? with????? the "Using registerPrefix with NFD" part of article "Application Development Documentation / Guides"[1].? ?The original text of the article goes as follows: >> >> >>> When you install NFD, it installs a default signing key on your system. For registerPrefix to create a signed command interest using this default signing key, your application needs to use the default KeyChain constructor and call setCommandSigningInfo so that the Face can sign the command interest created by registerPrefix >> >> ?But? ?when an application sends out a command interest, the recipient ?should check if the interest's signing key is finally signed by an ?administrator's signing key in order to reject unauthorized commands?.? >> >> So what's the purpose of the NFD's default signing key? Why should the app use this key? to initialize its identity?? Note the NFD's default signing key is not signed by anyone?[2].? >> >> If it is also? for defend?ing? against unauthorized command interests, then any local app, including possible malwares, can also use this key to sign their interest by simply using the default keychain. >> If not, what other purpose could it be? >> >> >> ?[1] https://redmine.named-data.net/projects/application-development-documentation-guides/wiki/Using_Client_Libraries_with_NDNx_vs_NDNx-TLV_vs_NFD#Using-registerPrefix-with-NFD >> ?[2] https://github.com/named-data/NFD/blob/master/tools/nfd-start.sh#L42 ? >> >> ? >> >> Thank you. ? >> -- >> Regards, >> Lei ?Pi >> University of Memphis? >> _______________________________________________ >> 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 wentaoshang at ucla.edu Wed Feb 22 21:36:01 2017 From: wentaoshang at ucla.edu (WENTAO SHANG) Date: Thu, 23 Feb 2017 05:36:01 +0000 Subject: [Ndn-interest] Questions about ndn porting to golang In-Reply-To: <3E1550D3-2A55-4A86-8272-F7924DA6A534@cs.ucla.edu> References: <857223EE-E5A2-4CA3-8FFD-635D5F2DD1F1@memphis.edu> <3E1550D3-2A55-4A86-8272-F7924DA6A534@cs.ucla.edu> Message-ID: I remember I had problem trying to match the golang concurrent programming model to NDN's async programming model. They seem to be incompatible with each other. If you program in Go, you need to think about the application logic in a much different way from you would do when programming in ndn-cxx or ndn-js. Wentao On Wed, Feb 22, 2017 at 9:29 PM Alex Afanasyev wrote: > I haven't worked with swig/go, but looked for it when some time ago > regarding python bindings. I didn't find it to be very easy to write swig > bindings and it looked a bit fragile and error-prone to use. > > For golang, I think using ndn-cxx library would defeat some of the > advantages that golang provides, specifically the concurrency. But I > agree, maintaining multiple libraries would be a lot of work. Though if > there are users for the library, the users themselves can try to do such > maintenance :-D > > -- > Alex > > On Feb 22, 2017, at 8:02 PM, Lei Pi (lpi) wrote: > > Hi everyone, > > While thinking about proposals for the coming NDN Hackathon, I?m curious > about the possibilities to write NDN applications in golang. > > There is a go-ndn project on github [1], which seems to be re-implementing > ndn in golang. But it is not officially supported or maintained. > > Another option for using ndn in golang is to link the binary with the > libndncxx / libndncpp library. [2][3][4] > > Does anyone already have experience in using SWIG to link golang programs > with libndncxx or libndncpp? > > [1] https://github.com/go-ndn/ndn > [2] https://golang.org/doc/faq#Do_Go_programs_link_with_Cpp_programs > [3] https://golang.org/cmd/cgo/ > [4] http://www.swig.org/Doc3.0/Go.html > > Thank you. > ---- > Regards, > Lei Pi > University of Memphis > Masters Student in Computer Science > > > _______________________________________________ > 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 tailinchu at gmail.com Wed Feb 22 22:31:16 2017 From: tailinchu at gmail.com (Tai-Lin Chu) Date: Wed, 22 Feb 2017 22:31:16 -0800 Subject: [Ndn-interest] Questions about ndn porting to golang In-Reply-To: <857223EE-E5A2-4CA3-8FFD-635D5F2DD1F1@memphis.edu> References: <857223EE-E5A2-4CA3-8FFD-635D5F2DD1F1@memphis.edu> Message-ID: Hi, I am the maintainer of go-ndn. I agree with Alex that ndn-cxx does not work well with go runtime. The main problems are thread-safety and memory management. For the programming model, I don't think it is entirely incompatible; this is a problem of designing an interface. I think (correct me if I am wrong) that all supported ndn libraries are designed to be async because the programming language cannot efficiently map async nature of networking to higher level abstraction. go encourages writing blocking code, which can be easily made async later with goroutine. If you look into go-ndn/ndn, lowest-level is still async, but higher level abstraction (go-ndn/mux) is synchronous, and handles one interest in a goroutine like go http library. go-ndn/ndn library is still maintained (we are going to release go-ndn 1.8 next week or so), and the api is more or less stable. I tried to keep this core library minimal, and the newer works are some higher level libraries that use it, like go-ndn/raft and go-ndn/mux. We and some other companies/organizations have been running this for a while now, so it should be good if you are trying to prototype some NDN applications in go for your hackathon. Ping me if you need to know more about mux and go-ndn/raft. If you are interested in go-ndn performance, you can also benchmark it, and hope you will find it quite "optimized" :) Thanks! On Wed, Feb 22, 2017 at 8:02 PM, Lei Pi (lpi) wrote: > Hi everyone, > > While thinking about proposals for the coming NDN Hackathon, I?m curious > about the possibilities to write NDN applications in golang. > > There is a go-ndn project on github [1], which seems to be re-implementing > ndn in golang. But it is not officially supported or maintained. > > Another option for using ndn in golang is to link the binary with the > libndncxx / libndncpp library. [2][3][4] > > Does anyone already have experience in using SWIG to link golang programs > with libndncxx or libndncpp? > > [1] https://github.com/go-ndn/ndn > [2] https://golang.org/doc/faq#Do_Go_programs_link_with_Cpp_programs > [3] https://golang.org/cmd/cgo/ > [4] http://www.swig.org/Doc3.0/Go.html > > Thank you. > ---- > Regards, > Lei Pi > University of Memphis > Masters Student in Computer Science > > > > > > _______________________________________________ > 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 Thu Feb 23 05:58:30 2017 From: lanwang at memphis.edu (Lan Wang (lanwang)) Date: Thu, 23 Feb 2017 13:58:30 +0000 Subject: [Ndn-interest] [Question] What's the purpose of the NFD's default signing key? In-Reply-To: <40644624-11D8-4D06-89D2-0E64E06A59CD@cs.ucla.edu> References: <40644624-11D8-4D06-89D2-0E64E06A59CD@cs.ucla.edu> Message-ID: <796DE247-9ABF-4854-B685-E3720FBA2377@memphis.edu> Alex, Thank you for the information. Just a few clarification questions: On Feb 22, 2017, at 11:22 PM, Alex Afanasyev > wrote: As Lan pointed out already, [1] is very old guide for NDNx codebase and many statements there don't apply to NFD. The "default" key that is created by nfd-start is only used to sign responses for NFD management requests and commands and current tools don't do validation of the responses. The applications and tools that want to register prefixes with NFD, they need to use keys that are authorized by NFD for this operation. Why and how do applications and tools get keys authorized by NFD? Does every application need to do this? Lan In our default deployment, we have a very relaxed policy to allow any local registrations, which can be tied up in nfd.conf. The default policy for "remote" registration (using /localhop/nfd) is to deny all and on our testbed nodes we require commands to be signed by a valid NDN Testbed certificate. --- Alex On Feb 21, 2017, at 10:55 AM, Lei Pi > wrote: Hi, While ?reading documents on redmine, I found myself confused ? with? ? ? ? ? the "Using registerPrefix with NFD" part of article "Application Development Documentation / Guides"[1]. ? ? The original text of the article goes as follows: >>> When you install NFD, it installs a default signing key on your system. For registerPrefix to create a signed command interest using this default signing key, your application needs to use the default KeyChain constructor and call setCommandSigningInfo so that the Face can sign the command interest created by registerPrefix ?But ? ? when an application sends out a command interest, the recipient ?should check if the interest's signing key is finally signed by an ?administrator's signing key in order to reject unauthorized commands ?.? So what's the purpose of the NFD's default signing key? Why should the app use this key ? to initialize its identity? ? Note the NFD's default signing key is not signed by anyone ?[2].? If it is also ? for defend ?ing? against unauthorized command interests, then any local app, including possible malwares, can also use this key to sign their interest by simply using the default keychain. If not, what other purpose could it be? ?[1] https://redmine.named-data.net/projects/application-development-documentation-guides/wiki/Using_Client_Libraries_with_NDNx_vs_NDNx-TLV_vs_NFD#Using-registerPrefix-with-NFD ?[2] https://github.com/named-data/NFD/blob/master/tools/nfd-start.sh#L42 ? ? Thank you. ? -- Regards, Lei ?Pi University of Memphis? _______________________________________________ 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 lpi at memphis.edu Thu Feb 23 07:49:03 2017 From: lpi at memphis.edu (Lei Pi) Date: Thu, 23 Feb 2017 09:49:03 -0600 Subject: [Ndn-interest] Questions about ndn porting to golang In-Reply-To: References: <857223EE-E5A2-4CA3-8FFD-635D5F2DD1F1@memphis.edu> Message-ID: Alex, Wentao, and Tai-Lin, Thank you very much for the information. So as a conclusion, it is not suggested to automate linking go programs to ndn-cxx, because concurrency and memory management will be a problem for the application. (Btw, SWIG 3.0 supports generating C++ code wrappers now, not sure if writing swig binding is still a problem.) It is more prefered to use and help maintain go-ndn to develop ndn applications. This project is currently maintained by Tai-Lin. On Thu, Feb 23, 2017 at 12:31 AM, Tai-Lin Chu wrote: > Hi, > I am the maintainer of go-ndn. I agree with Alex that ndn-cxx does not > work well with go runtime. The main problems are thread-safety and > memory management. > > For the programming model, I don't think it is entirely incompatible; > this is a problem of designing an interface. I think (correct me if I > am wrong) that all supported ndn libraries are designed to be async > because the programming language cannot efficiently map async nature > of networking to higher level abstraction. go encourages writing > blocking code, which can be easily made async later with goroutine. If > you look into go-ndn/ndn, lowest-level is still async, but higher > level abstraction (go-ndn/mux) is synchronous, and handles one > interest in a goroutine like go http library. > > go-ndn/ndn library is still maintained (we are going to release go-ndn > 1.8 next week or so), and the api is more or less stable. I tried to > keep this core library minimal, and the newer works are some higher > level libraries that use it, like go-ndn/raft and go-ndn/mux. We and > some other companies/organizations have been running this for a while > now, so it should be good if you are trying to prototype some NDN > applications in go for your hackathon. Ping me if you need to know > more about mux and go-ndn/raft. > > If you are interested in go-ndn performance, you can also benchmark > it, and hope you will find it quite "optimized" :) > > Thanks! > > > On Wed, Feb 22, 2017 at 8:02 PM, Lei Pi (lpi) wrote: > > Hi everyone, > > > > While thinking about proposals for the coming NDN Hackathon, I?m curious > > about the possibilities to write NDN applications in golang. > > > > There is a go-ndn project on github [1], which seems to be > re-implementing > > ndn in golang. But it is not officially supported or maintained. > > > > Another option for using ndn in golang is to link the binary with the > > libndncxx / libndncpp library. [2][3][4] > > > > Does anyone already have experience in using SWIG to link golang programs > > with libndncxx or libndncpp? > > > > [1] https://github.com/go-ndn/ndn > > [2] https://golang.org/doc/faq#Do_Go_programs_link_with_Cpp_programs > > [3] https://golang.org/cmd/cgo/ > > [4] http://www.swig.org/Doc3.0/Go.html > > > > Thank you. > > ---- > > Regards, > > Lei Pi > > University of Memphis > > Masters Student in Computer Science > > > > > > > > > > > > _______________________________________________ > > Ndn-interest mailing list > > Ndn-interest at lists.cs.ucla.edu > > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > > > -- Regards, Lei -------------- next part -------------- An HTML attachment was scrubbed... URL: From aa at CS.UCLA.EDU Thu Feb 23 08:07:48 2017 From: aa at CS.UCLA.EDU (Alex Afanasyev) Date: Thu, 23 Feb 2017 08:07:48 -0800 Subject: [Ndn-interest] [Question] What's the purpose of the NFD's default signing key? In-Reply-To: <796DE247-9ABF-4854-B685-E3720FBA2377@memphis.edu> References: <40644624-11D8-4D06-89D2-0E64E06A59CD@cs.ucla.edu> <796DE247-9ABF-4854-B685-E3720FBA2377@memphis.edu> Message-ID: <78122216-5511-45E5-8AD6-0628511204BF@cs.ucla.edu> > On Feb 23, 2017, at 5:58 AM, Lan Wang (lanwang) wrote: > > Alex, > > Thank you for the information. Just a few clarification questions: > >> On Feb 22, 2017, at 11:22 PM, Alex Afanasyev > wrote: >> >> As Lan pointed out already, [1] is very old guide for NDNx codebase and many statements there don't apply to NFD. >> >> The "default" key that is created by nfd-start is only used to sign responses for NFD management requests and commands and current tools don't do validation of the responses. The applications and tools that want to register prefixes with NFD, they need to use keys that are authorized by NFD for this operation. > > Why and how do applications and tools get keys authorized by NFD? Does every application need to do this? This is deployment issue. If NFD uses strict checking for prefix registration signatures, then all applications that want to publish would need to have keys. This either local trust anchor CA needs to issue certificates for local apps or keys of applications need to be explicitly trusted by NFD. -- Alex > > Lan > >> In our default deployment, we have a very relaxed policy to allow any local registrations, which can be tied up in nfd.conf. The default policy for "remote" registration (using /localhop/nfd) is to deny all and on our testbed nodes we require commands to be signed by a valid NDN Testbed certificate. >> >> --- >> Alex >> >>> On Feb 21, 2017, at 10:55 AM, Lei Pi > wrote: >>> >>> Hi, >>> >>> While ?reading documents on redmine, I found myself confused ? with? ? ? ? ? the "Using registerPrefix with NFD" part of article "Application Development Documentation / Guides"[1]. ? ? The original text of the article goes as follows: >>> >>> >>> When you install NFD, it installs a default signing key on your system. For registerPrefix to create a signed command interest using this default signing key, your application needs to use the default KeyChain constructor and call setCommandSigningInfo so that the Face can sign the command interest created by registerPrefix >>> >>> ?But ? ? when an application sends out a command interest, the recipient ?should check if the interest's signing key is finally signed by an ?administrator's signing key in order to reject unauthorized commands ?.? >>> >>> So what's the purpose of the NFD's default signing key? Why should the app use this key ? to initialize its identity? ? Note the NFD's default signing key is not signed by anyone ?[2].? >>> >>> If it is also ? for defend ?ing? against unauthorized command interests, then any local app, including possible malwares, can also use this key to sign their interest by simply using the default keychain. >>> If not, what other purpose could it be? >>> >>> >>> ?[1] https://redmine.named-data.net/projects/application-development-documentation-guides/wiki/Using_Client_Libraries_with_NDNx_vs_NDNx-TLV_vs_NFD#Using-registerPrefix-with-NFD >>> ?[2] https://github.com/named-data/NFD/blob/master/tools/nfd-start.sh#L42 ? >>> >>> ? >>> >>> Thank you. ? >>> -- >>> Regards, >>> Lei ?Pi >>> University of Memphis? >>> _______________________________________________ >>> 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 luca.muscariello at gmail.com Fri Feb 24 00:58:44 2017 From: luca.muscariello at gmail.com (Luca Muscariello) Date: Fri, 24 Feb 2017 09:58:44 +0100 Subject: [Ndn-interest] Fwd: Cisco Announces Important Steps toward Adoption of Information-Centric Networking In-Reply-To: References: Message-ID: http://blogs.cisco.com/sp/cisco-announces-important- steps-toward-adoption-of-information-centric-networking -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott1091 at yahoo.com Fri Feb 24 13:14:59 2017 From: scott1091 at yahoo.com (scott1091 at yahoo.com) Date: Fri, 24 Feb 2017 21:14:59 +0000 (UTC) Subject: [Ndn-interest] Design choice: naming scheme or packet payload? References: <222010749.247241.1487970899480.ref@mail.yahoo.com> Message-ID: <222010749.247241.1487970899480@mail.yahoo.com> Hi all, Thanks for accepting my request. I am working on a NDN forwarding strategy and consumer/producer applications on ndnSIM. Assuming that there are multiple paths from the consumer to a data source, the goal is to improve data delivery based on cross-layer information from the network, so the consumer can select the best face to send the following Interest packets based on number of hops, node ID, throughput, round-trip delay, and geographical location. I see two possible ways to implement that: 1. Insert the cross layer information direct in the packet payload ??? Every node along the path would have to update the packet payload or meta data accordingly, and the producer would insert its coordinates.??? The consumer can then select which face to send the following Interests based on throughput, or distance to content source, or path with less hops, etc.??? Since the NDN architecture doesn't allow the payload to be modified, intermediate nodes would have to create a copy of the packets. Can I use MetaInfo field? 2. Design a naming scheme (more common in the literature) ??? Use a naming scheme to accomodate that. For instance the Interest packet would be ///<+node_id> and the data packet would be something like ////, where node_id1-N refers to the nodes along the path. Are the two implementations feasible? Could you comment on the recommended way to use information from the network in the forwarding decision? Thank you! -------------- next part -------------- An HTML attachment was scrubbed... URL: From babaeim at clarkson.EDU Fri Feb 24 15:08:00 2017 From: babaeim at clarkson.EDU (Marzieh Babaeianjelodar) Date: Fri, 24 Feb 2017 18:08:00 -0500 Subject: [Ndn-interest] Question about NFD Installation Message-ID: Hi I have installed NFD on both nodes of linux virtual machines. I have done the configuration and installation steps given in getting started with ndn page but when I run ./consumer and ./producer I get the following message. Can someone please help figure out the problem? Sending /example/testApp/randomData?ndn.MustBeFresh=1&ndn.InterestLifetime=1000 received Nack with reason NoRoute for interest /example/testApp/randomData?ndn.MustBeFresh=1&ndn.InterestLifetime=1000&ndn.Nonce=2496501792 -------------- next part -------------- An HTML attachment was scrubbed... URL: From susmit at cs.colostate.edu Fri Feb 24 16:03:32 2017 From: susmit at cs.colostate.edu (Susmit) Date: Fri, 24 Feb 2017 17:03:32 -0700 Subject: [Ndn-interest] Question about NFD Installation In-Reply-To: References: Message-ID: Hi Marzieh, You will need to add a route between those two VMs. On VM1, you can try this: nfdc register /example/testApp udp4:// You might also want to look at the utilities here: https://named-data.net/doc/NFD/current/manpages.html On Fri, Feb 24, 2017 at 4:08 PM, Marzieh Babaeianjelodar wrote: > Hi > > I have installed NFD on both nodes of linux virtual machines. I have done > the configuration and installation steps given in getting started with ndn > page but when I run ./consumer and ./producer I get the following message. > Can someone please help figure out the problem? > > Sending > /example/testApp/randomData?ndn.MustBeFresh=1&ndn.InterestLifetime=1000 > received Nack with reason NoRoute for interest > /example/testApp/randomData?ndn.MustBeFresh=1&ndn.InterestLifetime=1000&ndn.Nonce=2496501792 > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > -- Regards, Susmit ==================================== http://www.cs.colostate.edu/~susmit ==================================== From shijunxiao at email.arizona.edu Fri Feb 24 21:21:56 2017 From: shijunxiao at email.arizona.edu (Junxiao Shi) Date: Fri, 24 Feb 2017 22:21:56 -0700 Subject: [Ndn-interest] Design choice: naming scheme or packet payload? In-Reply-To: <222010749.247241.1487970899480@mail.yahoo.com> References: <222010749.247241.1487970899480.ref@mail.yahoo.com> <222010749.247241.1487970899480@mail.yahoo.com> Message-ID: Hi Scott Neither Name nor MetaInfo should be modified on intermediate nodes. Instead, hop-by-hop information can appear as NDNLPv2 headers. NDNLP is a link protocol for NDN, specifically designed for carrying hop-by-hop information. You may find more information about NDNLPv2 on https://redmine.named-data.net/projects/nfd/wiki/NDNLPv2 Yours, Junxiao On Fri, Feb 24, 2017 at 2:14 PM, wrote: > Hi all, > > Thanks for accepting my request. > > I am working on a NDN forwarding strategy and consumer/producer > applications on ndnSIM. Assuming that there are multiple paths from the > consumer to a data source, the goal is to improve data delivery based on > cross-layer information from the network, so the consumer can select the > best face to send the following Interest packets based on number of hops, > node ID, throughput, round-trip delay, and geographical location. > > I see two possible ways to implement that: > 1. Insert the cross layer information direct in the packet payload > Every node along the path would have to update the packet payload or > meta data accordingly, and the producer would insert its coordinates. > The consumer can then select which face to send the following > Interests based on throughput, or distance to content source, or path with > less hops, etc. > Since the NDN architecture doesn't allow the payload to be modified, > intermediate nodes would have to create a copy of the packets. Can I use > MetaInfo field? > > 2. Design a naming scheme (more common in the literature) > Use a naming scheme to accomodate that. For instance the Interest > packet would be ///<+node_id> and the data > packet would be something like //// + node_id2 + ... + node_idN>, where node_id1-N refers to the nodes along > the path. > > Are the two implementations feasible? Could you comment on the recommended > way to use information from the network in the forwarding decision? > > Thank you! > -------------- next part -------------- An HTML attachment was scrubbed... URL: From babaeim at clarkson.edu Fri Feb 24 21:28:35 2017 From: babaeim at clarkson.edu (Marzieh Babaeianjelodar) Date: Sat, 25 Feb 2017 00:28:35 -0500 Subject: [Ndn-interest] Question about NDN Tools Message-ID: <1BEAFF67-F1FA-44BB-83D0-59C5775B5344@clarkson.edu> Hi I have installed the nan-tools but I don?t know how to run them. Like peek and ping. Can you help me. Best Regards, Marzieh From babaeim at clarkson.EDU Fri Feb 24 21:53:01 2017 From: babaeim at clarkson.EDU (Marzieh Babaeianjelodar) Date: Sat, 25 Feb 2017 00:53:01 -0500 Subject: [Ndn-interest] Question about NDN Tools In-Reply-To: <1BEAFF67-F1FA-44BB-83D0-59C5775B5344@clarkson.edu> References: <1BEAFF67-F1FA-44BB-83D0-59C5775B5344@clarkson.edu> Message-ID: <053711A8-0C5A-44E4-AE27-7FE7FA77B60B@clarkson.edu> I actually tried to do this: Typed echo 'HELLO WORLD' | ndnpoke ndn:/localhost/demo/hello on one node and typed ndnpeek -p ndn:/localhost/demo/hello on another node and tried to run it but nothing happened. > On Feb 25, 2017, at 12:28 AM, Marzieh Babaeianjelodar wrote: > > Hi > > I have installed the nan-tools but I don?t know how to run them. Like peek and ping. Can you help me. > > Best Regards, > > Marzieh -------------- next part -------------- An HTML attachment was scrubbed... URL: From philoliang2011 at gmail.com Sat Feb 25 09:45:59 2017 From: philoliang2011 at gmail.com (Teng Liang) Date: Sat, 25 Feb 2017 10:45:59 -0700 Subject: [Ndn-interest] Question about NDN Tools In-Reply-To: <053711A8-0C5A-44E4-AE27-7FE7FA77B60B@clarkson.edu> References: <1BEAFF67-F1FA-44BB-83D0-59C5775B5344@clarkson.edu> <053711A8-0C5A-44E4-AE27-7FE7FA77B60B@clarkson.edu> Message-ID: Hi Marzieh, To simply try the tools, just run them on local machine in different consoles. The programs are talking to local NFD, so remember to start NFD first. To try the tools on different nodes, one more step is needed, i.e., getting NFD on different nodes connected. You can find answers here https://named-data.net/2015/01/06/get-nfd-connected/. Best, Teng On Fri, Feb 24, 2017 at 10:53 PM, Marzieh Babaeianjelodar < babaeim at clarkson.edu> wrote: > I actually tried to do this: > > Typed echo 'HELLO WORLD' | ndnpoke ndn:/localhost/demo/hello on one node > and typed ndnpeek -p ndn:/localhost/demo/hello on another node and tried > to run it but nothing happened. > > > > On Feb 25, 2017, at 12:28 AM, Marzieh Babaeianjelodar < > babaeim at clarkson.edu> wrote: > > Hi > > I have installed the nan-tools but I don?t know how to run them. Like peek > and ping. Can you help me. > > Best Regards, > > Marzieh > > > > _______________________________________________ > 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 babaeim at clarkson.edu Sat Feb 25 19:55:43 2017 From: babaeim at clarkson.edu (Marzieh Babaeianjelodar) Date: Sat, 25 Feb 2017 22:55:43 -0500 Subject: [Ndn-interest] Question about NDN - chunks Message-ID: I have a question about how to run the chunks or segmented file transfer between producer and consumer. Can you help me with the process I have the ndn tools installed and this following page is what I am referring to but I feel like it is not enough for me. https://github.com/named-data/ndn-tools/tree/master/tools/chunks -------------- next part -------------- An HTML attachment was scrubbed... URL: From babaeim at clarkson.edu Sun Feb 26 10:15:43 2017 From: babaeim at clarkson.edu (Marzieh Babaeianjelodar) Date: Sun, 26 Feb 2017 13:15:43 -0500 Subject: [Ndn-interest] Send file NDND Message-ID: <9BB8ACD6-8377-4EE7-BDA2-59E481BD02A4@clarkson.edu> Hi One of the things I want to do is send my specific file from one consumer to producer which sends an interest packet and receives a data packet. Can you tell me which tool should I use for that? Best Regards, Marzieh From shijunxiao at email.arizona.EDU Sun Feb 26 10:25:32 2017 From: shijunxiao at email.arizona.EDU (Junxiao Shi) Date: Sun, 26 Feb 2017 11:25:32 -0700 Subject: [Ndn-interest] Send file NDND In-Reply-To: <9BB8ACD6-8377-4EE7-BDA2-59E481BD02A4@clarkson.edu> References: <9BB8ACD6-8377-4EE7-BDA2-59E481BD02A4@clarkson.edu> Message-ID: Hi Marzieh If you are working with the old ndnd (circa 2013), the tool you can use is ccnpeek and ccnpoke. The file size is limited to about 1200 octets. With NFD, you can use ndncatchucks which has no file size limit. The producer, ndnputchunks, will divide files into multiple Data packets. See https://github.com/named-data/ndn-tools/tree/master/tools/chunks Yours, Junxiao On Feb 26, 2017 11:16, "Marzieh Babaeianjelodar" wrote: Hi One of the things I want to do is send my specific file from one consumer to producer which sends an interest packet and receives a data packet. Can you tell me which tool should I use for that? Best Regards, Marzieh -------------- next part -------------- An HTML attachment was scrubbed... URL: From klaus at cs.arizona.EDU Sun Feb 26 11:51:23 2017 From: klaus at cs.arizona.EDU (Klaus Schneider) Date: Sun, 26 Feb 2017 12:51:23 -0700 Subject: [Ndn-interest] Question about NDN - chunks In-Reply-To: References: Message-ID: Did you try running the commands from the help file? Is there any specific part of the guide you have questions about, or any specific error message you get? Best regards, Klaus On 02/25/2017 08:55 PM, Marzieh Babaeianjelodar wrote: > I have a question about how to run the chunks or segmented file transfer > between producer and consumer. Can you help me with the process I have > the ndn tools installed and this following page is what I am referring > to but I feel like it is not enough for me. > https://github.com/named-data/ndn-tools/tree/master/tools/chunks > > > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > From klaus at cs.arizona.EDU Sun Feb 26 12:39:12 2017 From: klaus at cs.arizona.EDU (Klaus Schneider) Date: Sun, 26 Feb 2017 13:39:12 -0700 Subject: [Ndn-interest] Design choice: naming scheme or packet payload? In-Reply-To: References: <222010749.247241.1487970899480.ref@mail.yahoo.com> <222010749.247241.1487970899480@mail.yahoo.com> Message-ID: Hi Scott, I think we should also note that using NDNLP headers to modify information at intermediate nodes is more a workaround of the current implementation than a permanent requirement of NDN. The information you are talking about is relevant to the endpoints of the connection (consumer and producer), but seems completely irrelevant to the endpoints of each link on the path. Putting it inside NDNLP is, I think, to choose the wrong layer for the task. An analogy would be that you want a new feature in the IP protocol, let's say larger addresses. But instead of changing IPv4, you add the larger addresses to all the link/MAC layer protocols on the way and copy the information at each hop. This has two results: First, you bloat the link layer protocols with functionality that doesn't belong there. Second, you create a dependency for each newly invented link layer protocol to support the shared features (e.g. larger addresses). This failure of decoupling seems to be exactly what is happening with NDNLP. > NDN architecture doesn't allow the payload to be modified This is true for the current implementation. However, there might be use cases for allowing certain parts of the payload or certain metainfo to be modified at each node (by keeping them outside the "security envelope" of the packet). Given the bloating of NDNLP, maybe it's time to think about allowing intermediate nodes to manipulate well-defined parts of Interest and Data packets. Best regards, Klaus On 02/24/2017 10:21 PM, Junxiao Shi wrote: > Hi Scott > > Neither Name nor MetaInfo should be modified on intermediate nodes. > Instead, hop-by-hop information can appear as NDNLPv2 headers. > NDNLP is a link protocol for NDN, specifically designed for carrying > hop-by-hop information. You may find more information about NDNLPv2 > on https://redmine.named-data.net/projects/nfd/wiki/NDNLPv2 > > > Yours, Junxiao > > On Fri, Feb 24, 2017 at 2:14 PM, > wrote: > > Hi all, > > Thanks for accepting my request. > > I am working on a NDN forwarding strategy and consumer/producer > applications on ndnSIM. Assuming that there are multiple paths from > the consumer to a data source, the goal is to improve data delivery > based on cross-layer information from the network, so the consumer > can select the best face to send the following Interest packets > based on number of hops, node ID, throughput, round-trip delay, and > geographical location. > > I see two possible ways to implement that: > 1. Insert the cross layer information direct in the packet payload > Every node along the path would have to update the packet > payload or meta data accordingly, and the producer would insert its > coordinates. > The consumer can then select which face to send the following > Interests based on throughput, or distance to content source, or > path with less hops, etc. > Since the NDN architecture doesn't allow the payload to be > modified, intermediate nodes would have to create a copy of the > packets. Can I use MetaInfo field? > > 2. Design a naming scheme (more common in the literature) > Use a naming scheme to accomodate that. For instance the > Interest packet would be ///<+node_id> > and the data packet would be something like > //// node_idN>, where node_id1-N refers to the nodes along the path. > > Are the two implementations feasible? Could you comment on the > recommended way to use information from the network in the > forwarding decision? > > Thank you! > > > > _______________________________________________ > Ndn-interest mailing list > Ndn-interest at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > From klaus at cs.arizona.EDU Sun Feb 26 12:45:30 2017 From: klaus at cs.arizona.EDU (Klaus Schneider) Date: Sun, 26 Feb 2017 13:45:30 -0700 Subject: [Ndn-interest] Question about NDN - chunks In-Reply-To: <5B6FD130-215F-445B-B6D8-BCD9CE57FAF3@clarkson.edu> References: <5B6FD130-215F-445B-B6D8-BCD9CE57FAF3@clarkson.edu> Message-ID: <3bc41cc2-453c-6e84-dcf3-ef699c983ad5@cs.arizona.edu> I think the ndnputchunks command you used worked fine, but it doesn't print any output by default. It might be a good idea to change this default though. You can use "ndnputchunks -v" to see a message when the application has finished publishing the file. Best regards, Klaus P.S. It would be better if you copied the text into the email instead of using pictures, since they disappear in a text-only reply. On 02/26/2017 01:05 PM, Marzieh Babaeianjelodar wrote: > Ok lemme tell you what exactly I am doing. > > I installed the ndn-tools on both nodes as you can see here: > > > And they are compiled and the chunks are in the bin of build as you can > see in the following: > > > Now based on the link > https://github.com/named-data/ndn-tools/tree/master/tools/chunks I have > to run the ndncatchunks and ndnputchunks. > So I run this following command but I do not get anything published. > Besides I do not understand this command. Can you clarify it? > > > When I run this following command I get something published though: > > >> On Feb 26, 2017, at 2:51 PM, Klaus Schneider > > wrote: >> >> Did you try running the commands from the help file? >> >> Is there any specific part of the guide you have questions about, or >> any specific error message you get? >> >> Best regards, >> Klaus >> >> >> On 02/25/2017 08:55 PM, Marzieh Babaeianjelodar wrote: >>> I have a question about how to run the chunks or segmented file transfer >>> between producer and consumer. Can you help me with the process I have >>> the ndn tools installed and this following page is what I am referring >>> to but I feel like it is not enough for me. >>> https://github.com/named-data/ndn-tools/tree/master/tools/chunks >>> >>> >>> >>> _______________________________________________ >>> Ndn-interest mailing list >>> Ndn-interest at lists.cs.ucla.edu >>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest >>> > From klaus at cs.arizona.edu Sun Feb 26 14:33:29 2017 From: klaus at cs.arizona.edu (Klaus Schneider) Date: Sun, 26 Feb 2017 15:33:29 -0700 Subject: [Ndn-interest] Question about NDN - chunks In-Reply-To: <4EB9C1A6-5D21-4284-A583-6F04E6D5AE7D@clarkson.edu> References: <5B6FD130-215F-445B-B6D8-BCD9CE57FAF3@clarkson.edu> <3bc41cc2-453c-6e84-dcf3-ef699c983ad5@cs.arizona.edu> <4EB9C1A6-5D21-4284-A583-6F04E6D5AE7D@clarkson.edu> Message-ID: <930dd9b7-a40e-796c-86b3-7b6e50cdbaf6@cs.arizona.edu> The path of the file should be piped into the ndncatchunks command. Thus is should be: ndnputchunks -v ndn:/prefix/fileip.txt < /Users/marzieh/Desktop/fileip.txt This will publish your file under the NDN name "/prefix/fileip.txt". So you can run "ndncatchunks -v /prefix/fileip.txt". There is no need for you to include the GPL-3 license. Best regards, Klaus On 02/26/2017 01:58 PM, Marzieh Babaeianjelodar wrote: > Thanks yes I just used -v and it gave me something > > Now if I want to send my own file that I made on the desktop which the > name is ?fileip? and the path is ?/Users/marzieh/Desktop/fileip.txt? do > I have to run this command? > > ndnputchunks -v ndn:/Users/marzieh/Desktop/fileip.txt < > /usr/share/common-licenses/GPL-3 > > >> On Feb 26, 2017, at 3:45 PM, Klaus Schneider > > wrote: >> >> I think the ndnputchunks command you used worked fine, but it doesn't >> print any output by default. It might be a good idea to change this >> default though. >> >> You can use "ndnputchunks -v" to see a message when the application >> has finished publishing the file. >> >> Best regards, >> Klaus >> >> >> P.S. It would be better if you copied the text into the email instead >> of using pictures, since they disappear in a text-only reply. >> >> >> On 02/26/2017 01:05 PM, Marzieh Babaeianjelodar wrote: >>> Ok lemme tell you what exactly I am doing. >>> >>> I installed the ndn-tools on both nodes as you can see here: >>> >>> >>> And they are compiled and the chunks are in the bin of build as you can >>> see in the following: >>> >>> >>> Now based on the link >>> https://github.com/named-data/ndn-tools/tree/master/tools/chunks I have >>> to run the ndncatchunks and ndnputchunks. >>> So I run this following command but I do not get anything published. >>> Besides I do not understand this command. Can you clarify it? >>> >>> >>> When I run this following command I get something published though: >>> >>> >>>> On Feb 26, 2017, at 2:51 PM, Klaus Schneider >>> >>>> > wrote: >>>> >>>> Did you try running the commands from the help file? >>>> >>>> Is there any specific part of the guide you have questions about, or >>>> any specific error message you get? >>>> >>>> Best regards, >>>> Klaus >>>> >>>> >>>> On 02/25/2017 08:55 PM, Marzieh Babaeianjelodar wrote: >>>>> I have a question about how to run the chunks or segmented file >>>>> transfer >>>>> between producer and consumer. Can you help me with the process I have >>>>> the ndn tools installed and this following page is what I am referring >>>>> to but I feel like it is not enough for me. >>>>> https://github.com/named-data/ndn-tools/tree/master/tools/chunks >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Ndn-interest mailing list >>>>> Ndn-interest at lists.cs.ucla.edu >>>>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest > From babaeim at clarkson.EDU Sun Feb 26 15:50:20 2017 From: babaeim at clarkson.EDU (Marzieh Babaeianjelodar) Date: Sun, 26 Feb 2017 18:50:20 -0500 Subject: [Ndn-interest] Ndn- peek Message-ID: <03AECF2F-C02B-4632-8106-F4559745F8F3@clarkson.edu> Hi In the following command which uses ndnpoke and ndnpeek is reponse and they are transmitting a single packet between consumer and producer. what path /localhost/demo/hello is this? Is it the path of a text file that I have to make just like chunk in nfd? echo 'HELLO WORLD' | ndnpoke ndn:/localhost/demo/hello -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott1091 at yahoo.com Sun Feb 26 16:55:45 2017 From: scott1091 at yahoo.com (scott1091 at yahoo.com) Date: Mon, 27 Feb 2017 00:55:45 +0000 (UTC) Subject: [Ndn-interest] Design choice: naming scheme or packet payload? In-Reply-To: References: <222010749.247241.1487970899480.ref@mail.yahoo.com> <222010749.247241.1487970899480@mail.yahoo.com> Message-ID: <1077704726.1392249.1488156945505@mail.yahoo.com> Thank you both for your answers. I believe that the packet information field in the NDNLP is useful for my application. The endpoints can handle the remaining features. I will let you know of any suggestions or struggles in the near future. On Sunday, February 26, 2017 3:48 PM, Klaus Schneider wrote: Hi Scott, I think we should also note that using NDNLP headers to modify information at intermediate nodes is more a workaround of the current implementation than a permanent requirement of NDN. The information you are talking about is relevant to the endpoints of the connection (consumer and producer), but seems completely irrelevant to the endpoints of each link on the path. Putting it inside NDNLP is, I think, to choose the wrong layer for the task. An analogy would be that you want a new feature in the IP protocol, let's say larger addresses. But instead of changing IPv4, you add the larger addresses to all the link/MAC layer protocols on the way and copy the information at each hop. This has two results: First, you bloat the link layer protocols with functionality that doesn't belong there. Second, you create a dependency for each newly invented link layer protocol to support the shared features (e.g. larger addresses). This failure of decoupling seems to be exactly what is happening with NDNLP. > NDN architecture doesn't allow the payload to be modified This is true for the current implementation. However, there might be use cases for allowing certain parts of the payload or certain metainfo to be modified at each node (by keeping them outside the "security envelope" of the packet). Given the bloating of NDNLP, maybe it's time to think about allowing intermediate nodes to manipulate well-defined parts of Interest and Data packets. Best regards, Klaus On 02/24/2017 10:21 PM, Junxiao Shi wrote: > Hi Scott > > Neither Name nor MetaInfo should be modified on intermediate nodes. > Instead, hop-by-hop information can appear as NDNLPv2 headers. > NDNLP is a link protocol for NDN, specifically designed for carrying > hop-by-hop information. You may find more information about NDNLPv2 > on https://redmine.named-data.net/projects/nfd/wiki/NDNLPv2 > > > Yours, Junxiao > > On Fri, Feb 24, 2017 at 2:14 PM, > wrote: > >? ? Hi all, > >? ? Thanks for accepting my request. > >? ? I am working on a NDN forwarding strategy and consumer/producer >? ? applications on ndnSIM. Assuming that there are multiple paths from >? ? the consumer to a data source, the goal is to improve data delivery >? ? based on cross-layer information from the network, so the consumer >? ? can select the best face to send the following Interest packets >? ? based on number of hops, node ID, throughput, round-trip delay, and >? ? geographical location. > >? ? I see two possible ways to implement that: >? ? 1. Insert the cross layer information direct in the packet payload >? ? ? ? Every node along the path would have to update the packet >? ? payload or meta data accordingly, and the producer would insert its >? ? coordinates. >? ? ? ? The consumer can then select which face to send the following >? ? Interests based on throughput, or distance to content source, or >? ? path with less hops, etc. >? ? ? ? Since the NDN architecture doesn't allow the payload to be >? ? modified, intermediate nodes would have to create a copy of the >? ? packets. Can I use MetaInfo field? > >? ? 2. Design a naming scheme (more common in the literature) >? ? ? ? Use a naming scheme to accomodate that. For instance the >? ? Interest packet would be ///<+node_id> >? ? and the data packet would be something like >? ? ////? ? node_idN>, where node_id1-N refers to the nodes along the path. > >? ? Are the two implementations feasible? Could you comment on the >? ? recommended way to use information from the network in the >? ? forwarding decision? > >? ? Thank you! > > > > _______________________________________________ > 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 babaeim at clarkson.edu Mon Feb 27 07:56:31 2017 From: babaeim at clarkson.edu (Marzieh Babaeianjelodar) Date: Mon, 27 Feb 2017 10:56:31 -0500 Subject: [Ndn-interest] Face URI Message-ID: <102FB054-649F-44F9-8EDC-90E80D2EEA9B@clarkson.edu> Hi In NDN what does face URI stand for and what does it mean? From babaeim at clarkson.edu Mon Feb 27 08:19:46 2017 From: babaeim at clarkson.edu (Marzieh Babaeianjelodar) Date: Mon, 27 Feb 2017 11:19:46 -0500 Subject: [Ndn-interest] Question about NDN Tools In-Reply-To: References: <1BEAFF67-F1FA-44BB-83D0-59C5775B5344@clarkson.edu> <053711A8-0C5A-44E4-AE27-7FE7FA77B60B@clarkson.edu> <129B6EF3-BBE4-44F8-8825-66384D2DE24A@clarkson.edu> Message-ID: Ok. > On Feb 27, 2017, at 11:18 AM, Teng Liang wrote: > > Can you reply to the mailing list, so that other people can learn from it as well. > > Best, > Teng > > On Sat, Feb 25, 2017 at 6:49 PM, Marzieh Babaeianjelodar > wrote: > Thank you that page helped a lot > > But when I run this following > > nfdc register /example udp4://spurs.cs.ucla.edu <> > > It is successful but when I run this following: > > ndnping /ndn/edu/arizona > > I get this: > nack from /example/edu/arizona: seq=3632876897692409981 time=1.25708 ms reason=NoRoute > > Can you help me with this? > > >> On Feb 25, 2017, at 12:45 PM, Teng Liang > wrote: >> >> Hi Marzieh, >> >> To simply try the tools, just run them on local machine in different consoles. The programs are talking to local NFD, so remember to start NFD first. >> >> To try the tools on different nodes, one more step is needed, i.e., getting NFD on different nodes connected. You can find answers here https://named-data.net/2015/01/06/get-nfd-connected/ . >> >> Best, >> Teng >> >> On Fri, Feb 24, 2017 at 10:53 PM, Marzieh Babaeianjelodar > wrote: >> I actually tried to do this: >> >> Typed echo 'HELLO WORLD' | ndnpoke ndn:/localhost/demo/hello on one node and typed ndnpeek -p ndn:/localhost/demo/hello on another node and tried to run it but nothing happened. >> >> >> >>> On Feb 25, 2017, at 12:28 AM, Marzieh Babaeianjelodar > wrote: >>> >>> Hi >>> >>> I have installed the nan-tools but I don?t know how to run them. Like peek and ping. Can you help me. >>> >>> Best Regards, >>> >>> Marzieh >> >> >> _______________________________________________ >> 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 Feb 27 09:32:50 2017 From: shijunxiao at email.arizona.EDU (Junxiao Shi) Date: Mon, 27 Feb 2017 10:32:50 -0700 Subject: [Ndn-interest] Face URI In-Reply-To: <102FB054-649F-44F9-8EDC-90E80D2EEA9B@clarkson.edu> References: <102FB054-649F-44F9-8EDC-90E80D2EEA9B@clarkson.edu> Message-ID: Hi Marzieh FaceUri is not part of NDN architecture, but it's used in NFD implementation to identify a *face*. See NFD developer guide, face system - transport section for more information. Yours, Junxiao On Mon, Feb 27, 2017 at 8:56 AM, Marzieh Babaeianjelodar < babaeim at clarkson.edu> wrote: > Hi > > In NDN what does face URI stand for and what does it mean? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From babaeim at clarkson.edu Mon Feb 27 11:44:14 2017 From: babaeim at clarkson.edu (Marzieh Babaeianjelodar) Date: Mon, 27 Feb 2017 14:44:14 -0500 Subject: [Ndn-interest] Ndn chunk Message-ID: <983E495D-7CCA-4AF6-96A3-E62A138F65F2@clarkson.edu> When I was running ndn chunks it was working yesterday but now it is not and gives me this: what is the problem? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-02-27 at 2.43.22 PM.png Type: image/png Size: 117464 bytes Desc: not available URL: From shijunxiao at email.arizona.EDU Mon Feb 27 12:53:20 2017 From: shijunxiao at email.arizona.EDU (Junxiao Shi) Date: Mon, 27 Feb 2017 13:53:20 -0700 Subject: [Ndn-interest] Ndn chunk In-Reply-To: <983E495D-7CCA-4AF6-96A3-E62A138F65F2@clarkson.edu> References: <983E495D-7CCA-4AF6-96A3-E62A138F65F2@clarkson.edu> Message-ID: Hi Marzieh Thanks for reporting this. I am able to reproduce the problem, and it's now tracked as ndn-tools Bug #3981 . You may watch this issue on Redmine to get progress updates. Yours, Junxiao On Mon, Feb 27, 2017 at 12:44 PM, Marzieh Babaeianjelodar < babaeim at clarkson.edu> wrote: > When I was running ndn chunks it was working yesterday but now it is not > and gives me this: what is the problem? > > > _______________________________________________ > 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: Screen Shot 2017-02-27 at 2.43.22 PM.png Type: image/png Size: 117464 bytes Desc: not available URL: From klaus at cs.arizona.EDU Mon Feb 27 13:29:05 2017 From: klaus at cs.arizona.EDU (Klaus Schneider) Date: Mon, 27 Feb 2017 14:29:05 -0700 Subject: [Ndn-interest] Ndn chunk In-Reply-To: References: <983E495D-7CCA-4AF6-96A3-E62A138F65F2@clarkson.edu> Message-ID: Also, a workaround for you would be to keep the ndnputchunks process running in the background. Klaus On 02/27/2017 01:53 PM, Junxiao Shi wrote: > Hi Marzieh > > Thanks for reporting this. I am able to reproduce the problem, and it's > now tracked as ndn-tools Bug #3981 > . You may watch this issue > on Redmine to get progress updates. > > Yours, Junxiao > > On Mon, Feb 27, 2017 at 12:44 PM, Marzieh Babaeianjelodar > > wrote: > > When I was running ndn chunks it was working yesterday but now it is > not and gives me this: what is the problem? > > > _______________________________________________ > 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 babaeim at clarkson.EDU Mon Feb 27 13:54:46 2017 From: babaeim at clarkson.EDU (Marzieh Babaeianjelodar) Date: Mon, 27 Feb 2017 16:54:46 -0500 Subject: [Ndn-interest] Ndn chunk In-Reply-To: References: <983E495D-7CCA-4AF6-96A3-E62A138F65F2@clarkson.edu> Message-ID: <664709A1-D146-4EA9-B759-2D7D21E629F4@clarkson.edu> Thanks. I fixed the problem. It was a stupid misspell between the name ?example" and ?examples?. > On Feb 27, 2017, at 4:29 PM, Klaus Schneider wrote: > > Also, a workaround for you would be to keep the ndnputchunks process running in the background. > > Klaus > > > On 02/27/2017 01:53 PM, Junxiao Shi wrote: >> Hi Marzieh >> >> Thanks for reporting this. I am able to reproduce the problem, and it's >> now tracked as ndn-tools Bug #3981 >> . You may watch this issue >> on Redmine to get progress updates. >> >> Yours, Junxiao >> >> On Mon, Feb 27, 2017 at 12:44 PM, Marzieh Babaeianjelodar >> > wrote: >> >> When I was running ndn chunks it was working yesterday but now it is >> not and gives me this: what is the problem? >> >> >> _______________________________________________ >> 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 babaeim at clarkson.edu Mon Feb 27 15:50:28 2017 From: babaeim at clarkson.edu (Marzieh Babaeianjelodar) Date: Mon, 27 Feb 2017 18:50:28 -0500 Subject: [Ndn-interest] NDN question Message-ID: <44C28AC5-0ECE-490D-9994-FA2E8D390504@clarkson.edu> Hi When we use this command which says to find the published version you have to use -p what does it mean? I know it gives me some thing like this: babaeim at consumer:~$ ndnputchunks -p ndn:/example/fileip.txt < /users/babaeim/fileip.txt %FD%00%00%01Z%81%F8%82%F I want to know what is this published version? Best Regards, Marzieh -------------- next part -------------- An HTML attachment was scrubbed... URL: From babaeim at clarkson.edu Mon Feb 27 16:03:06 2017 From: babaeim at clarkson.edu (Marzieh Babaeianjelodar) Date: Mon, 27 Feb 2017 19:03:06 -0500 Subject: [Ndn-interest] NDN question In-Reply-To: <44C28AC5-0ECE-490D-9994-FA2E8D390504@clarkson.edu> References: <44C28AC5-0ECE-490D-9994-FA2E8D390504@clarkson.edu> Message-ID: <68892981-2B09-4D1D-A57B-CDF2C0B03C8B@clarkson.edu> So from what I understand this data is getting published each time with a different version like if I RUN the command different times it will give me different versions and different published version. Is that right? > On Feb 27, 2017, at 6:50 PM, Marzieh Babaeianjelodar wrote: > > Hi > > When we use this command which says to find the published version you have to use -p what does it mean? > > I know it gives me some thing like this: > > babaeim at consumer:~$ ndnputchunks -p ndn:/example/fileip.txt < /users/babaeim/fileip.txt > %FD%00%00%01Z%81%F8%82%F > > I want to know what is this published version? > > Best Regards, > > Marzieh -------------- next part -------------- An HTML attachment was scrubbed... URL: From babaeim at clarkson.EDU Mon Feb 27 16:43:11 2017 From: babaeim at clarkson.EDU (Marzieh Babaeianjelodar) Date: Mon, 27 Feb 2017 19:43:11 -0500 Subject: [Ndn-interest] NDN - Question Message-ID: <06806BB2-C69F-4295-9817-3256597F385E@clarkson.edu> Hi I have ran the ndnchunk command and it is working but if I WANT TO by any chance change a name what is the simplest way? Just register a name through the nfdc command? From babaeim at clarkson.EDU Mon Feb 27 16:55:03 2017 From: babaeim at clarkson.EDU (Marzieh Babaeianjelodar) Date: Mon, 27 Feb 2017 19:55:03 -0500 Subject: [Ndn-interest] NDN chunk Message-ID: <7FC71E3E-390A-4DE6-9640-425C553A927F@clarkson.edu> What is the difference between these two commands: ndncatchunks -d iterative ndn:/localhost/demo/gpl3 ndncatchunks -v ndn:/localhost/demo/gpl3 -------------- next part -------------- An HTML attachment was scrubbed... URL: From babaeim at clarkson.EDU Mon Feb 27 18:22:01 2017 From: babaeim at clarkson.EDU (Marzieh Babaeianjelodar) Date: Mon, 27 Feb 2017 21:22:01 -0500 Subject: [Ndn-interest] NDN chunk In-Reply-To: References: <7FC71E3E-390A-4DE6-9640-425C553A927F@clarkson.edu> Message-ID: <8B117642-E64D-41DB-ABA6-D3450130A1DB@clarkson.edu> Thanks it was very helpful. I have another question. What if we change the file and update it and we want to retrieve the old file with an older version? Can we just run the command with the version name? > On Feb 27, 2017, at 8:13 PM, Nick Briggs wrote: > > Run "ndncatchunks -h" for the help text... most of the tools have -h or --help options. > > From the help for ndncatchunks -- > "-d" does version discovery and takes argument "fixed" or "iterative". > "-v" turns on verbose output but doesn't affect the NDN packets sent vs. not having "-v". > Each time you publish data with ndnputchunks it will create a new version -- the new version number is what gets printed with the "-p" option. The individual packets that compose what you think of as a "file" are going to be named as (using your example below) > /localhost/demo/gpl3// > where the version and chunk components are binary coded (plus a leading marker) representations of the values. > > Look at the documentation (or look at the source for the command line parsing...) for how to turn on packet logging for the NDN forwarding daemon -- then you can see exactly what's going on at the packet level when you run ndnputchunks/ndncatchunks (or any other NDN command that's talking to the forwarding daemon) > > -- Nick Briggs > > >> On Feb 27, 2017, at 4:55 PM, Marzieh Babaeianjelodar > wrote: >> >> What is the difference between these two commands: >> ndncatchunks -d iterative ndn:/localhost/demo/gpl3 >> >> ndncatchunks -v ndn:/localhost/demo/gpl3 >> >> _______________________________________________ >> 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 babaeim at clarkson.EDU Mon Feb 27 18:48:37 2017 From: babaeim at clarkson.EDU (Marzieh Babaeianjelodar) Date: Mon, 27 Feb 2017 21:48:37 -0500 Subject: [Ndn-interest] NDN chunk In-Reply-To: <8B117642-E64D-41DB-ABA6-D3450130A1DB@clarkson.edu> References: <7FC71E3E-390A-4DE6-9640-425C553A927F@clarkson.edu> <8B117642-E64D-41DB-ABA6-D3450130A1DB@clarkson.edu> Message-ID: <3CA9A71E-9AB2-4C55-85EF-A12D54C9867B@clarkson.edu> Ok I think I got my answer to that question. We can get it through "-d fixed?. > On Feb 27, 2017, at 9:22 PM, Marzieh Babaeianjelodar wrote: > > Thanks it was very helpful. > > I have another question. What if we change the file and update it and we want to retrieve the old file with an older version? Can we just run the command with the version name? > >> On Feb 27, 2017, at 8:13 PM, Nick Briggs > wrote: >> >> Run "ndncatchunks -h" for the help text... most of the tools have -h or --help options. >> >> From the help for ndncatchunks -- >> "-d" does version discovery and takes argument "fixed" or "iterative". >> "-v" turns on verbose output but doesn't affect the NDN packets sent vs. not having "-v". >> Each time you publish data with ndnputchunks it will create a new version -- the new version number is what gets printed with the "-p" option. The individual packets that compose what you think of as a "file" are going to be named as (using your example below) >> /localhost/demo/gpl3// >> where the version and chunk components are binary coded (plus a leading marker) representations of the values. >> >> Look at the documentation (or look at the source for the command line parsing...) for how to turn on packet logging for the NDN forwarding daemon -- then you can see exactly what's going on at the packet level when you run ndnputchunks/ndncatchunks (or any other NDN command that's talking to the forwarding daemon) >> >> -- Nick Briggs >> >> >>> On Feb 27, 2017, at 4:55 PM, Marzieh Babaeianjelodar > wrote: >>> >>> What is the difference between these two commands: >>> ndncatchunks -d iterative ndn:/localhost/demo/gpl3 >>> >>> ndncatchunks -v ndn:/localhost/demo/gpl3 >>> >>> _______________________________________________ >>> 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 babaeim at clarkson.edu Mon Feb 27 19:13:23 2017 From: babaeim at clarkson.edu (Marzieh Babaeianjelodar) Date: Mon, 27 Feb 2017 22:13:23 -0500 Subject: [Ndn-interest] NDN chunk In-Reply-To: <3CA9A71E-9AB2-4C55-85EF-A12D54C9867B@clarkson.edu> References: <7FC71E3E-390A-4DE6-9640-425C553A927F@clarkson.edu> <8B117642-E64D-41DB-ABA6-D3450130A1DB@clarkson.edu> <3CA9A71E-9AB2-4C55-85EF-A12D54C9867B@clarkson.edu> Message-ID: Ok. Now I have another question about this part of the documentation: When I run the following command two times, and I give the second time the old specific version %FD%00%00%01Z%82%AF%A4%EF , with the ndncatchunks I still get the latest version. I mean what is this command good for? Why do we need to publish an old version data again when we can just retrieve it with ndncatchunks -d fixed? I hope you understood my question To publish data with a specific version, you must append a version component to the end of the prefix. The version component must follow the aforementioned NDN naming conventions. For example, the following command will publish the version %FD%00%00%01Qc%CF%17v of the /localhost/demo/gpl3 prefix: ndnputchunks ndn:/localhost/demo/gpl3/%FD%00%00%01Qc%CF%17v < /usr/share/common-licenses/GPL-3 > On Feb 27, 2017, at 9:48 PM, Marzieh Babaeianjelodar wrote: > > Ok I think I got my answer to that question. We can get it through "-d fixed?. > >> On Feb 27, 2017, at 9:22 PM, Marzieh Babaeianjelodar > wrote: >> >> Thanks it was very helpful. >> >> I have another question. What if we change the file and update it and we want to retrieve the old file with an older version? Can we just run the command with the version name? >> >>> On Feb 27, 2017, at 8:13 PM, Nick Briggs > wrote: >>> >>> Run "ndncatchunks -h" for the help text... most of the tools have -h or --help options. >>> >>> From the help for ndncatchunks -- >>> "-d" does version discovery and takes argument "fixed" or "iterative". >>> "-v" turns on verbose output but doesn't affect the NDN packets sent vs. not having "-v". >>> Each time you publish data with ndnputchunks it will create a new version -- the new version number is what gets printed with the "-p" option. The individual packets that compose what you think of as a "file" are going to be named as (using your example below) >>> /localhost/demo/gpl3// >>> where the version and chunk components are binary coded (plus a leading marker) representations of the values. >>> >>> Look at the documentation (or look at the source for the command line parsing...) for how to turn on packet logging for the NDN forwarding daemon -- then you can see exactly what's going on at the packet level when you run ndnputchunks/ndncatchunks (or any other NDN command that's talking to the forwarding daemon) >>> >>> -- Nick Briggs >>> >>> >>>> On Feb 27, 2017, at 4:55 PM, Marzieh Babaeianjelodar > wrote: >>>> >>>> What is the difference between these two commands: >>>> ndncatchunks -d iterative ndn:/localhost/demo/gpl3 >>>> >>>> ndncatchunks -v ndn:/localhost/demo/gpl3 >>>> >>>> _______________________________________________ >>>> 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 nicholas.h.briggs at gmail.com Mon Feb 27 19:22:17 2017 From: nicholas.h.briggs at gmail.com (Nick Briggs) Date: Mon, 27 Feb 2017 19:22:17 -0800 Subject: [Ndn-interest] NDN chunk In-Reply-To: References: <7FC71E3E-390A-4DE6-9640-425C553A927F@clarkson.edu> <8B117642-E64D-41DB-ABA6-D3450130A1DB@clarkson.edu> <3CA9A71E-9AB2-4C55-85EF-A12D54C9867B@clarkson.edu> Message-ID: I don't think I quite understand your question, but what the documentation is saying is that you can either let ndnputchunks create a version (when you don't give one), or you can give the desired version explicitly (as long as it follows the correct format -- %FD followed by 8 bytes). It doesn't make any sense to *re*publish something under a name & version that has already been published (assuming it still exists somewhere). -- Nick > On Feb 27, 2017, at 7:13 PM, Marzieh Babaeianjelodar wrote: > > Ok. Now I have another question about this part of the documentation: > > When I run the following command two times, and I give the second time the old specific version %FD%00%00%01Z%82%AF%A4%EF , with the ndncatchunks I still get the latest version. I mean what is this command good for? Why do we need to publish an old version data again when we can just retrieve it with ndncatchunks -d fixed? > > I hope you understood my question > > To publish data with a specific version, you must append a version component to the end of the prefix. The version component must follow the aforementioned NDN naming conventions. For example, the following command will publish the version %FD%00%00%01Qc%CF%17v of the /localhost/demo/gpl3 prefix: > > ndnputchunks ndn:/localhost/demo/gpl3/%FD%00%00%01Qc%CF%17v < /usr/share/common-licenses/GPL-3I don > > >> On Feb 27, 2017, at 9:48 PM, Marzieh Babaeianjelodar > wrote: >> >> Ok I think I got my answer to that question. We can get it through "-d fixed?. >> >>> On Feb 27, 2017, at 9:22 PM, Marzieh Babaeianjelodar > wrote: >>> >>> Thanks it was very helpful. >>> >>> I have another question. What if we change the file and update it and we want to retrieve the old file with an older version? Can we just run the command with the version name? >>> >>>> On Feb 27, 2017, at 8:13 PM, Nick Briggs > wrote: >>>> >>>> Run "ndncatchunks -h" for the help text... most of the tools have -h or --help options. >>>> >>>> From the help for ndncatchunks -- >>>> "-d" does version discovery and takes argument "fixed" or "iterative". >>>> "-v" turns on verbose output but doesn't affect the NDN packets sent vs. not having "-v". >>>> Each time you publish data with ndnputchunks it will create a new version -- the new version number is what gets printed with the "-p" option. The individual packets that compose what you think of as a "file" are going to be named as (using your example below) >>>> /localhost/demo/gpl3// >>>> where the version and chunk components are binary coded (plus a leading marker) representations of the values. >>>> >>>> Look at the documentation (or look at the source for the command line parsing...) for how to turn on packet logging for the NDN forwarding daemon -- then you can see exactly what's going on at the packet level when you run ndnputchunks/ndncatchunks (or any other NDN command that's talking to the forwarding daemon) >>>> >>>> -- Nick Briggs >>>> >>>> >>>>> On Feb 27, 2017, at 4:55 PM, Marzieh Babaeianjelodar > wrote: >>>>> >>>>> What is the difference between these two commands: >>>>> ndncatchunks -d iterative ndn:/localhost/demo/gpl3 >>>>> >>>>> ndncatchunks -v ndn:/localhost/demo/gpl3 >>>>> >>>>> _______________________________________________ >>>>> 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 babaeim at clarkson.EDU Mon Feb 27 19:52:21 2017 From: babaeim at clarkson.EDU (Marzieh Babaeianjelodar) Date: Mon, 27 Feb 2017 22:52:21 -0500 Subject: [Ndn-interest] NDN chunk In-Reply-To: References: <7FC71E3E-390A-4DE6-9640-425C553A927F@clarkson.edu> <8B117642-E64D-41DB-ABA6-D3450130A1DB@clarkson.edu> <3CA9A71E-9AB2-4C55-85EF-A12D54C9867B@clarkson.edu> Message-ID: <419B84DD-A2F4-4191-AA05-75A2963E670B@clarkson.edu> Ok thank you. I got my answer from your answer. Sorry for asking a lot of questions. There are interest pipeline types which are ?fixed? and ?aimd? can you describe that because I don?t understand it from the documentation and I DON?T get anything different from running each. Thanks > On Feb 27, 2017, at 10:22 PM, Nick Briggs wrote: > > I don't think I quite understand your question, but what the documentation is saying is that you can either let ndnputchunks create a version (when you don't give one), or you can give the desired version explicitly (as long as it follows the correct format -- %FD followed by 8 bytes). It doesn't make any sense to *re*publish something under a name & version that has already been published (assuming it still exists somewhere). > > -- Nick > > >> On Feb 27, 2017, at 7:13 PM, Marzieh Babaeianjelodar > wrote: >> >> Ok. Now I have another question about this part of the documentation: >> >> When I run the following command two times, and I give the second time the old specific version %FD%00%00%01Z%82%AF%A4%EF , with the ndncatchunks I still get the latest version. I mean what is this command good for? Why do we need to publish an old version data again when we can just retrieve it with ndncatchunks -d fixed? >> >> I hope you understood my question >> >> To publish data with a specific version, you must append a version component to the end of the prefix. The version component must follow the aforementioned NDN naming conventions. For example, the following command will publish the version %FD%00%00%01Qc%CF%17v of the /localhost/demo/gpl3 prefix: >> >> ndnputchunks ndn:/localhost/demo/gpl3/%FD%00%00%01Qc%CF%17v < /usr/share/common-licenses/GPL-3I don >> >> >>> On Feb 27, 2017, at 9:48 PM, Marzieh Babaeianjelodar > wrote: >>> >>> Ok I think I got my answer to that question. We can get it through "-d fixed?. >>> >>>> On Feb 27, 2017, at 9:22 PM, Marzieh Babaeianjelodar > wrote: >>>> >>>> Thanks it was very helpful. >>>> >>>> I have another question. What if we change the file and update it and we want to retrieve the old file with an older version? Can we just run the command with the version name? >>>> >>>>> On Feb 27, 2017, at 8:13 PM, Nick Briggs > wrote: >>>>> >>>>> Run "ndncatchunks -h" for the help text... most of the tools have -h or --help options. >>>>> >>>>> From the help for ndncatchunks -- >>>>> "-d" does version discovery and takes argument "fixed" or "iterative". >>>>> "-v" turns on verbose output but doesn't affect the NDN packets sent vs. not having "-v". >>>>> Each time you publish data with ndnputchunks it will create a new version -- the new version number is what gets printed with the "-p" option. The individual packets that compose what you think of as a "file" are going to be named as (using your example below) >>>>> /localhost/demo/gpl3// >>>>> where the version and chunk components are binary coded (plus a leading marker) representations of the values. >>>>> >>>>> Look at the documentation (or look at the source for the command line parsing...) for how to turn on packet logging for the NDN forwarding daemon -- then you can see exactly what's going on at the packet level when you run ndnputchunks/ndncatchunks (or any other NDN command that's talking to the forwarding daemon) >>>>> >>>>> -- Nick Briggs >>>>> >>>>> >>>>>> On Feb 27, 2017, at 4:55 PM, Marzieh Babaeianjelodar > wrote: >>>>>> >>>>>> What is the difference between these two commands: >>>>>> ndncatchunks -d iterative ndn:/localhost/demo/gpl3 >>>>>> >>>>>> ndncatchunks -v ndn:/localhost/demo/gpl3 >>>>>> >>>>>> _______________________________________________ >>>>>> 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 babaeim at clarkson.EDU Mon Feb 27 20:25:07 2017 From: babaeim at clarkson.EDU (Marzieh Babaeianjelodar) Date: Mon, 27 Feb 2017 23:25:07 -0500 Subject: [Ndn-interest] Name ndn Message-ID: I have a question about when I RUN THIS following command: So I know the name is in this form: /example/fileip.txt// But I want to know more about the structure of version and chunk ?? I also need someone to describe Metainfo line for me Thanks babaeim at producer:~$ ndncatchunks -v /example/fileip.txt Data: Name: /example/fileip.txt/%FD%00%00%01Z%82%E3L%20/%00%00 MetaInfo: ContentType: 0, FreshnessPeriod: 10000 milliseconds, FinalBlockId: %00%00 Content: (size: 78) Signature: (type: 1, value_length: 256) -------------- next part -------------- An HTML attachment was scrubbed... URL: From mahsa.aghajani at gmail.com Tue Feb 28 05:16:26 2017 From: mahsa.aghajani at gmail.com (Mahsa Aghajani) Date: Tue, 28 Feb 2017 16:46:26 +0330 Subject: [Ndn-interest] Sync and NLSR Message-ID: Hello everyone, 1- In "Let's Chronosync" there is a mention of digest log, which keeps track of merkle tree changes and its history. Which part of sync code, exacltly, responds to this log? 2- Does nlsr also form digest log at all? If so, what's the use of it for nlsr? Is the overhead of keeping it negligible? Thanks -- Mahsa Aghajani M.Sc. Student Department of Computer Engineering Sharif University of Technology -------------- next part -------------- An HTML attachment was scrubbed... URL: From lanwang at memphis.edu Tue Feb 28 07:21:11 2017 From: lanwang at memphis.edu (Lan Wang (lanwang)) Date: Tue, 28 Feb 2017 15:21:11 +0000 Subject: [Ndn-interest] Sync and NLSR In-Reply-To: References: Message-ID: <17B9C6DA-6871-49C6-AD0C-1D2E2E86434D@memphis.edu> On Feb 28, 2017, at 7:16 AM, Mahsa Aghajani > wrote: Hello everyone, 1- In "Let's Chronosync" there is a mention of digest log, which keeps track of merkle tree changes and its history. Which part of sync code, exacltly, responds to this log? 2- Does nlsr also form digest log at all? If so, what's the use of it for nlsr? Is the overhead of keeping it negligible? NLSR uses chronosync as a library. It doesn?t directly manage or operate on the digest log. Lan Thanks -- Mahsa Aghajani M.Sc. Student Department of Computer Engineering Sharif University of Technology _______________________________________________ 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 babaeim at clarkson.edu Tue Feb 28 08:56:15 2017 From: babaeim at clarkson.edu (Marzieh Babaeianjelodar) Date: Tue, 28 Feb 2017 11:56:15 -0500 Subject: [Ndn-interest] Name ndn In-Reply-To: References: Message-ID: <6F4323E3-22E5-41C1-91FD-C511B144CCE7@clarkson.edu> Thank you I did read through some of it. So in, min suffix component and max suffix component I have a interest name: example/fileip.txt/%FD%00%00%01Z%85%8B%86%DE Why is it saying minsuffix and maxsuffix are 3? Because 1/2/3 ? Because the document says beyond prefix. > On Feb 28, 2017, at 1:29 AM, Nick Briggs wrote: > > Marzieh -- I think you could read the NDN documentation, or papers, or the original papers about CCN, to get a basic understanding first... > > A content packet is composed of a name, some metadata, the actual payload, and the signature. > > The metadata can contain a bunch of different things, but what typically gets put in there is the content type, the freshness, the final block id (if it's part of a sequence), the "creation date/time" of the object (which may be of the file, or of signing, or ... whatever makes sense), the key locator (usually you'd put that in once in one of the first blocks sent). If ndncatchunks is putting out all the metainfo then ndnputchunks didn't put in a lot of interesting info. > > The %FD indicates that the component is a version number, and following that should be some number of bytes that represent the version... In the original CCNx code we didn't pad it out to 8 bytes, it was only enough bytes as necessary to represent the version number. > > The chunk number is in a canonical form with the minimal number of bytes starting with a leading 0 byte to represent the chunk number, so -- > 0 %00 > 1 %00%01 > 2 %00%02 > ... > 255 %00%FF > 256 %00%01%00 > etc. > > -- Nick > > > > >> On Feb 27, 2017, at 8:25 PM, Marzieh Babaeianjelodar > wrote: >> >> I have a question about when I RUN THIS following command: >> >> So I know the name is in this form: /example/fileip.txt// >> >> But I want to know more about the structure of version and chunk ?? >> >> I also need someone to describe Metainfo line for me >> >> Thanks >> >> babaeim at producer:~$ ndncatchunks -v /example/fileip.txt >> Data: Name: /example/fileip.txt/%FD%00%00%01Z%82%E3L%20/%00%00 >> MetaInfo: ContentType: 0, FreshnessPeriod: 10000 milliseconds, FinalBlockId: %00%00 >> Content: (size: 78) >> Signature: (type: 1, value_length: 256) >> _______________________________________________ >> 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 babaeim at clarkson.edu Tue Feb 28 09:02:02 2017 From: babaeim at clarkson.edu (Marzieh Babaeianjelodar) Date: Tue, 28 Feb 2017 12:02:02 -0500 Subject: [Ndn-interest] Exclude question Message-ID: Hi I have a question about how to use exclude? I read the documentation and understand that I can exclude one part from the name, how do I add that exclusion to my command? Because by default in the exclude this is what it gives me: and I WANT TO give it a specific thing. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2017-02-28 at 11.59.46 AM.png Type: image/png Size: 118515 bytes Desc: not available URL: