From shijunxiao at email.arizona.edu  Wed Mar  1 09:44:14 2017
From: shijunxiao at email.arizona.edu (Junxiao Shi)
Date: Wed, 1 Mar 2017 10:44:14 -0700
Subject: [Ndn-interest] Exclude question
In-Reply-To: <B9A35604-BA27-4787-8543-B5A47A8823C3@clarkson.edu>
References: <B9A35604-BA27-4787-8543-B5A47A8823C3@clarkson.edu>
Message-ID: <CAOFH+OYrvrwVaUctiSkDiyhhSqCveAN7x9jNSdAXJChbV52FZA@mail.gmail.com>

Hi Marzieh

ndncatchunks does not allow you to set Exclude selector via command line.
You may use ndn-traffic-generator
<https://github.com/named-data/ndn-traffic-generator> which allows you to
specify Exclude from a configuration file.

Yours, Junxiao

On Tue, Feb 28, 2017 at 10:02 AM, Marzieh Babaeianjelodar <
babaeim at clarkson.edu> wrote:

> 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: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170301/192d959c/attachment-0001.html>
-------------- 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: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170301/192d959c/attachment-0001.png>

From susmit at cs.colostate.edu  Wed Mar  1 19:25:57 2017
From: susmit at cs.colostate.edu (Susmit)
Date: Wed, 1 Mar 2017 20:25:57 -0700
Subject: [Ndn-interest] 4th NDN Hackathon - Call for Hacks
In-Reply-To: <CAM4XVkqPr=30j6xcWux=dT+=K+Gns6X4uvDy6N_33QkLWhXc+w@mail.gmail.com>
References: <CAM4XVkqG+wd+0HEPVNg8OqFARN89XPGg-Vz6Wqm--3aKh0e6dg@mail.gmail.com>
	<CAM4XVkqPr=30j6xcWux=dT+=K+Gns6X4uvDy6N_33QkLWhXc+w@mail.gmail.com>
Message-ID: <CAM4XVkqndruRUTCeLH2r=ms0=EPehxubssu_Vea-LSkb+zkVWQ@mail.gmail.com>

Hi All,

We have extended the deadline for proposal submission to March 8th. The new
notification date is March 12th.

So far, we have not received enough proposals for a Hackathon. If you are
attending, please consider submitting a proposal.

Thanks.

On Wed, Feb 22, 2017 at 10:35 AM, Susmit <susmit at cs.colostate.edu> wrote:

> 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 <susmit at cs.colostate.edu> 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
> ====================================
>



-- 

Regards,
Susmit

====================================
http://www.cs.colostate.edu/~susmit
====================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170301/8ea3d883/attachment.html>

From i.psaras at ucl.ac.uk  Thu Mar  2 04:49:22 2017
From: i.psaras at ucl.ac.uk (Psaras, Ioannis)
Date: Thu, 2 Mar 2017 12:49:22 +0000
Subject: [Ndn-interest] CFP: Workshop on Information-Centric Fog Computing
 (ICFC) at IFIP Networking 2017
Message-ID: <4BA23F3C-CE1C-45AC-9ADB-C1ADFAE7AD7C@live.ucl.ac.uk>

Dear colleagues,

please note deadline extension to 13th of March.

Best regards,
Yiannis.

? New deadline March 13th ?

====== Call For Papers ======

Workshop on Information-Centric Fog Computing (ICFC)
(in conjunction with IFIP Networking 2017)

12-16 June 2017, Stockholm, Sweden

Web: http://networking.ifip.org/2017/index.php/workshops/workshop-on-information-centric-fog-computing-icfc

=== Overview ===

Fog Computing aims to support the Internet of Things (IoT) through ultra low latency, ultra fast data processing, high security and reliability and highly efficient resource utilisation. However, the current approaches to Fog/Edge Computing have raised some concerns with respect to privacy; for example, extending CDN DNS redirection and private key delegation models to numerous applications increases the likelihood of exposing the edge to further attacks. There is also the challenge of supporting hierarchical and/or multi-access scenarios that go beyond traditional telco-controlled access provision. Furthermore, providing compute resources at the VM-level of granularity may not be suitable for some lightweight and short-lived functions, especially for IoT. These challenges call for alternative networking models that can support higher fluidity in distributing in-network functions, in addition to allowing fast and scalable processing and exchange of information.

Over the recent years, Information-centric Networking (ICN) has emerged as a networking paradigm that places information exchange, for the purpose of its processing, in the foreground. ICN brings advantages related to the security, management and dissemination of information, through flexible and information-based routing policies; combining these advantages with the ability to temporarily and spatially decouple communication entities, ICN seems well suited for the Fog Computing paradigm, since computation can happen at the right place any time by virtue of publishing and subscribing to it.

This workshop aims at stimulating research focused on the networking models, communication frameworks and security solutions required to facilitate Fog Computing. The research directions will focus on accommodating the requirements of data processing and information networking within emerging, information-focused, networking paradigms such as ICN. This is reflected in a number of aspects, including: enabling short-term content caching, fluid distribution of in-network functions, high-speed data analysis, programmable control and management planes, resiliency and security of fog networks, Machine-to-Machine (M2M) communications, coordinated management, resource consumption, privacy and orchestration of data processing and information production. The outcomes of the workshop should levitate communication frameworks that have the ability to accommodate the immense expansion of business models, applications and services, within future Fog networks.

The workshop solicits papers that address aspects of the above areas with a main focus on facilitating networking solutions that enable dynamic and flexible fog networking through joining concepts of softwarisation and virtualisation paradigms for better management and dissemination of information. We encourage papers that address cross-?layer research issues in any combination of these areas, bridging the gaps between IoT, Fog/edge Computing, ICN, Network Function Virtualisation (NFV) and SDN.



=== Topics of Interest ===

The list of topics include (but are not limited to):
?      Information-Centric Fog models
?      Content and service distribution models in Fog computing
?      Caching, replication and relaying models in Information-centric Fog networks
?      Dynamic in-network computation, e.g., Named Function Networking
?      Implementation insights of Fog & Information-?centric Networking architectures
?      Virtualisation in Fog systems and Information?-centric Networking
?      Security and privacy challenges in Fog computing
?      Novel compensation models, such as utilising block-chains
?      Computation and communication abstractions
?      Orchestration across computation, storage and communication resources for Fog networks
?      IoT  data storage, analysis and networking in cloud-based ICN
?      Programmability in Fog networks
?      Fog computing in constrained networks
?      Testing and evaluation tools
?      Self-?organisation/configuration of Fog resources using Information-?centric approaches
?      Traffic models for Information?-centric Fog networks
?      Theoretical and experimental evaluation of information-?centric networks used for Fog computing

=== Important Dates ===

?      Submission deadline: March 13, 2017
?      Acceptance notification: April 10, 2017
?      Program available online: April 19, 2017
?      Camera ready deadline: April 27, 2017


=== Submission Guidelines ===

All submissions should be written in the English language, with a maximum length limit of 6 printed pages (IEEE two-column format, 10pt), including all the figures, references, and appendices.
Submission implies the willingness of at least one author to attend the workshop and present the paper. Accepted papers will be included in the proceedings of IFIP ICFC 2017 and published in the IFIP.
Further details on the required paper format, as well as a link to the EDAS submission site can be found at the workshop?s website.




=== Committees ===

++ Workshop Chairs ++

George Polyzos, Athens University of Economics and Business
Dirk Trossen, InterDigital Europe
Kun Yang, University of Essex

++ Technical Program Chairs ++

Dirk Kutscher, Huawei
Ioannis Psaras, University College London

++ Organising Committee ++

Mays AL-Naday, University of Essex
Pekka Nikander, Ll co-op, Aalto University
B?rje Ohlman, Ericsson Research
Martin J Reed, University of Essex

++ Technical Program Committee ++

Mohammed AL-Khalidi, University of Essex
Mays AL-Naday, University of Essex
Shingo Ata, Osaka University
Giovanna Carofiglio, Cisco
Toru Hasegawa, Osaka University
Petri Laari, Ericsson Research
Chathura Magurawalage, University of Essex
Nicola Blefari Melazzi, University of Rome ? Tor Vergata
Marc Mosko, PARC
B?rje Ohlman, Ericsson Research
Christos Papadopoulos, Colorado State University
Michalis Polychronakis, Stony Brook University
Ioannis Psaras, University College London
Janne Riihij?rvi, RWTH Aachen University
Eve Schooler, Intel (US)
Nikos Thomos, University of Essex
Dirk Trossen, InterDigital Europe
Gareth Tyson, Queen Mary University of London
Matthias W?hlisch, Freie Universit?t Berlin
Cedric Westphal, Huawei (US)
Mick Wilson, Fujitsu (UK)
George Xylomenos, Athens University of Economics and Business
Lixia Zhang, UCLA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170302/43bb6de8/attachment-0001.html>

From agawande at memphis.edu  Fri Mar  3 11:00:11 2017
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Fri, 3 Mar 2017 19:00:11 +0000
Subject: [Ndn-interest] Mini-NDN v0.3.0 release
Message-ID: <BN3PR04MB2196EFE99CAD732F1258765ED92B0@BN3PR04MB2196.namprd04.prod.outlook.com>

Dear all,

We are pleased to announce the release of Mini-NDN (v0.3.0).

Mini-NDN is a lightweight networking emulation tool that enables testing, experimentation,
and research on the NDN platform. Based on Mininet, Mini-NDN uses the NDN libraries,
NFD, NLSR, and tools released by the NDN project (http://named-data.net/codebase/platform/)
to emulate an NDN network on a single system.

Detailed release notes with included features can be found at:
https://github.com/named-data/mini-ndn/blob/master/docs/RELEASE-NOTES.md

More information about Mini-NDN, tutorials, installation and configuration guides, and documentation
are available at the Mini-NDN Github repository:
https://github.com/named-data/mini-ndn

Please report any bugs or issues, make feature requests, or provide feedback at our Redmine page:
http://redmine.named-data.net/projects/mini-ndn

* * *
Mini-NDN Developers and Contributors:
  Ashlesh Gawande, Vince Lehman, Muktadir R Chowdhury, Nicholas Gordon
  Lan Wang, Alexander Afanasyev,
  Junxiao Shi, Beichuan Zhang


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

From n.boubakr at BIT.edu.cn  Tue Mar  7 23:44:25 2017
From: n.boubakr at BIT.edu.cn (Boubakr NOUR)
Date: Wed, 8 Mar 2017 15:44:25 +0800
Subject: [Ndn-interest] Duplicate Content Sharing
Message-ID: <b717e007-ee10-dfe0-960e-02ff42db4836@bit.edu.cn>

Hello,

I?d like to know how ICN network can treat the same shared content with 
different names.
Assuming that I?m sharing a document or a video with name *X*, the 
_*same *__*content *_can be shared in someplace by someone else using 
another name *Y*, and so on.
How can ICN treat this case!

Best regards,


-- 
Boubakr NOUR (Ph.D Candidate)
School of Computer Science
Beijing Institute of Technology
Office: Room 109, Information Building
5 South Zhongguancun Street, Haidian Dist., Beijing, China 100081
Email: n.boubakr at bit.edu.cn
Cell: +86-13261691266

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

From lanwang at memphis.edu  Wed Mar  8 05:13:51 2017
From: lanwang at memphis.edu (Lan Wang (lanwang))
Date: Wed, 8 Mar 2017 13:13:51 +0000
Subject: [Ndn-interest] NDNcomm 2017 Program
In-Reply-To: <5CE5D287-6D1D-4457-AC25-82F65D7F344E@memphis.edu>
References: <41bae7ba-c38b-40aa-a68e-082f9132bd20@emhub4.ad.ucla.edu>
	<21C3757D-FF98-433B-9419-955BED1BC9BF@memphis.edu>
	<BY2PR0401MB17015B07135F710C00C7CEC3D38E0@BY2PR0401MB1701.namprd04.prod.outlook.com>
	<5CE5D287-6D1D-4457-AC25-82F65D7F344E@memphis.edu>
Message-ID: <FA48E031-F030-46AE-924F-FB1723F4330E@memphis.edu>

Hi all,

Below is the NDNcomm 2017 program.  If you are interested in attending the meeting, please register at https://www.caida.org/workshops/ndn/1703/register.xml

Thanks.

Lan

March 22 (Wednesday)
NDN Project Retreat (NDN project members only)
Fishbowl Conference Room (Room 203/205), FedEx Institute of Technology

NDN Consortium Meeting (NDN Consortium members only)
Video Conference Center (Room 313), FedEx Institute of Technology

  *   08:00 - 17:00 NDN Retreat (NDN project members only)
  *   17:30 - 20:00 NDN Consortium Meeting (NDN Consortium members only)

March 23 (Thursday)
The Zone, FedEx Institute of Technology

  *   07:30 - 08:30 Breakfast
  *   08:30 - 09:20 NDNcomm Keynote: Past Achievements and Future Plan
  *   09:20 - 09:40 Break
  *   09:40 - 10:40 Mobile, IoT and Challenged Environments (Session Chair: Beichuan Zhang)
     *   NDN operation in Opportunistic Wireless Networks, Seweryn Dynerowicz, Omar Aponte, Paulo Mendes (COPELABS, University Lusofona)
     *   NFD-Android: NDN Networking Stack for Android Platform, Haitao Zhang, Alex Afanasyev, Lixia Zhang (UCLA)
     *   Internet of (Named) Things: NDN Protocol Stack for RIOT-OS, Wentao Shang, Alex Afanasyev, Lixia Zhang (UCLA)
     *   Opportunities for NDN in Augmented Reality, Jeff Burke (UCLA)
     *   Low-Rate Communications for Neighborhood Solar Over NDN, Alex Afanasyev, Jeff Thompson (UCLA)
  *   10:40 - 11:00 Break
  *   11:00 - 12:00 Data-Intensive Applications (Session Chair: Christos Papadopoulos)
     *   Deployment of SDTMA-NDN: A Scientific Data Transfer Management Architecture using Named Data Networking, Mohammad Alhowaidi, Byrav Ramamurthy, Brian Bockelman, David Swanson (Department of Computer Science and Engineering, University of Nebraska-Lincoln)
     *   Quantifying NDN's improvement to Scientific Data Management, Susmit Shannigrahi, Chengyu Fan, Christos Papadopoulos (CSU)
     *   From Crowd to Cloud: Apply Named Data Networking Principles to Manage Air Sensor Data, Yifang Zhu, Alex Afanasyev and Lixia Zhang (UCLA)
     *   Hadoop on Named Data Networking: Initial Experience and Results, Mathias Gibbens, Chris Gniady, Lei Ye, Beichuan Zhang (University of Arizona)
  *   12:00 - 13:30 Lunch
  *   13:30 - 14:30 Panel: NDN Security - Current Status and Open Issues
     *   Dante Pacella (Verizon) (pending confirmation)
     *   Alex Afanasyev (UCLA)
     *   Alex Halderman (U. Michigan)
     *   Satyajayant Misra (New Mexico State University)
  *   14:30 - 15:30 All Aspects of NDN (Session Chair: Lotfi Benmohamed)
     *   NFD Control Center: NDN Networking Stack and Security Enabler for Desktop Systems, Qi Zhao, Alex Afanasyev, Lixia Zhang (UCLA)
     *   Facilitating ICN Deployment with an Extended OpenFlow Protocol, Piotr Zuraniewski, Ray van Brandenburg (TNO); Borgert van der Kluit (Chess Wise); Niels van Adrichem (TNO)
     *   NDNS: DNS-Like Name Service for NDN, Yumin Xia, Alex Afanasyev, Lixia Zhang (UCLA)
     *   Adaptive Caching Algorithms with Optimality Guarantees for NDN Networks, Stratis Ioannidis, Edmund Yeh (Northeastern University)
     *   The State of the NDN Testbed, John DeHart (Washington University)
  *   15:30 - 16:00 Break
  *   16:00 - 17:00 Lightning Talks Introducing Posters and Demos (Session Chair: Josh Polterock)
     *   Demo: Integrating Named Data Networking with Transportation Simulation, Meng Kuai, Pawan Subedi, Xiaoyan Hong, Bing Zhou (The University of Alabama)
     *   Demo: Implementing an environmental sensor system using ICN, Bengt Ahlgren, Anders Lindgren (Swedish ICT - SICS); Adeel Mohammad Malik (Ericsson Research); Edith Ngai (Uppsala University); Borje Ohlman (Ericsson Research)
     *   Demo: NDN operation in Opportunistic Wireless Networks, Seweryn Dynerowicz, Omar Aponte, Paulo Mendes (COPELABS, University Lusofona)
     *   Demo: Securing Smart Homes in NDN, Lei Pi, Lan Wang (University of Memphis)
     *   Demo: Scalable Real-time Communication over NDN using Edge Service Routers, Syed Obaid Amin (Huawei Research Center); Haitao Zhang (UCLA); Asit Chakraborti, Aytac Azgin, Ravishankar Ravindran, GQ Wang (Huawei Research Center)
     *   Demo: Mini-NDN: a Lightweight and Scalable Emulation Environment for NDN, Ashlesh Gawande, Lan Wang (University of Memphis)
     *   Demo: NDN-RTC/Flume, Peter Gusev (UCLA)
     *   Demo: Open mHealth, Haitao Zhang, Zhehao Wang (UCLA)
     *   Poster: Secure Information Sharing among Autonomous Vehicles, Muktadir Chowdhury, Ashlesh Gawande, Lan Wang (University of Memphis)
     *   Poster: Controlling Strategy Retransmissions in Named Data Networking, Hila Ben Abraham, Patrick Crowley (Washington University in St. Louis)
     *   Poster: Network Measurement for Named Data Networking, Davide Pesavento, Omar Ilias El Mimouni, Lotfi Benmohamed (NIST)
     *   Poster: Path tracing in named-data networking, Siham KHOUSSI, Lotfi Benmohamed (NIST)
     *   Poster: NDN Distributed File System(NDFS), Junior DONGO, Charif MAHMOUDI, Fabrice MOURLIN (Paris-Est University)
     *   Poster: NDN for Cog Network to Support Next Generation Social Systems, Arata Koike, Yoshiko Sueda (Nippon Telegraph and Telephone Corp.)
     *   Poster: Named Data Networking of Things: Example Application .FLOW., Zhehao Wang, Eitan Mendelowitz, Zoe Sandoval, Jeff Burke (UCLA)
     *   Demo: NFD-Android: NDN Networking Stack for Android Platform, Haitao Zhang, Alex Afanasyev, Lixia Zhang (UCLA)
     *   Demo: NFD Control Center: NDN Networking Stack and Security Enabler for Desktop Systems, Qi Zhao, Alex Afanasyev, Lixia Zhang (UCLA)
     *   Demo: Facilitating ICN Deployment with an Extended OpenFlow Protocol, Piotr Zuraniewski, Ray van Brandenburg (TNO); Borgert van der Kluit (Chess Wise); Niels van Adrichem (TNO)
  *   17:00 - 20:00 Posters, Demo and Dinner

March 24 (Friday)
The Zone, FedEx Institute of Technology

  *   07:30 - 08:30 Breakfast
  *   08:30 - 09:30 NDNcomm: Community Feedback
  *   09:30 - 10:30 NDN Applications (Session Chair: Jeff Burke)
     *   ChronoShare: Decentralized File Sharing Application over NDN, Yukai Tu, Alex Afanasyev, Lixia Zhang (UCLA)
     *   nTorrent: Peer-to-Peer File Sharing in Named Data Networking, Spyridon Mastorakis, Alexander Afanasyev (UCLA); Yingdi Yu (Facebook, Inc); Lixia Zhang (UCLA)
     *   NDN-RTC and Experimental Library Functionality, Peter Gusev, Jeff Thompson, Alex Afanasyev (UCLA)
     *   Common Client Libraries - Update, Jeff Thompson, Jeff Burke (UCLA)
  *   10:30 - 11:00 Break
  *   11:00 - 12:00 Routing and Forwarding (Session Chair: GQ Wang)
     *   Geohyperbolic Routing and Addressing Schemes For Overlay Networks, Ivan Voitalov, Rodrigo Aldecoa (Northeastern University); Lan Wang (University of Memphis); Dmitri Krioukov (Northeastern University)
     *   How to Establish Loop-Free Multipath Routes in Named Data Networking, Klaus Schneider, Beichuan Zhang (The University of Arizona)
     *   A Native Content Discovery Mechanism for NDN, Onur Ascigil, Vasilis Sourlas, Ioannis Psaras, George Pavlou (University College London)
     *   ICN Geolocation Beacon Service, Dante Pacella, Ashish Sardesai, Mani Tadayon (Verizon)
  *   12:00 - 13:30 Lunch
  *   13:30 - 14:30 Panel: Rolling out NDN: who are the first movers with the most gain?
     *   Lixia Zhang (UCLA)
     *   Sokwoo Rhee (NIST)

  *   17:00 - 18:00 NDN Hackathon Welcome/Project pitches/Group formation
     *   See Hackathon page<http://4th-ndn-hackathon.named-data.net/> for more details.


Lan

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

From lixia at CS.UCLA.EDU  Wed Mar  8 06:52:39 2017
From: lixia at CS.UCLA.EDU (Lixia Zhang)
Date: Wed, 8 Mar 2017 06:52:39 -0800
Subject: [Ndn-interest] Duplicate Content Sharing
In-Reply-To: <b717e007-ee10-dfe0-960e-02ff42db4836@bit.edu.cn>
References: <b717e007-ee10-dfe0-960e-02ff42db4836@bit.edu.cn>
Message-ID: <1D7241EC-C257-460E-9F90-3E7944184664@cs.ucla.edu>


> On Mar 7, 2017, at 11:44 PM, Boubakr NOUR <n.boubakr at BIT.edu.cn> wrote:
> 
> Hello,
> 
> I?d like to know how ICN network can treat the same shared content with different names.
> Assuming that I?m sharing a document or a video with name X, the same content can be shared in someplace by someone else using another name Y, and so on.
> How can ICN treat this case!
> 
Keep in mind that NDN is a network layer protocol, given an Interest packet with a name, NDN will try to return a Data packet. Routers at network layer would not know the above mentioned video content got 2 different names.
Please let me know if this answered your question.

Lixia

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

From mayutan.arumaithurai at gmail.com  Wed Mar  8 05:32:26 2017
From: mayutan.arumaithurai at gmail.com (Mayutan A.)
Date: Wed, 8 Mar 2017 14:32:26 +0100
Subject: [Ndn-interest] CFP: 4th ACM Conference on Information-Centric
 Networking (ACM ICN-2017), Berlin, Germany, September 26-28,
 2017 (Deadline: 8 May 2017)
Message-ID: <CAADkTf1dUsFHCWzJsgtfRAoCDFzNfEsusgfMH6DECfQ7zp=J7A@mail.gmail.com>

---------------------------------------------------------------------------------------------------
ACM ICN 2017 Call For Papers
http://conferences.sigcomm.org/acm-icn/2017/cfp.html
----------------------------------------------------------------------------------------------------
The organizing committee is delighted to invite you to submit your work for
presentation at the 4th ACM conference on Information Centric Networking
(ACM ICN-2017), to be held in Berlin, Germany from September 26-28, 2017.

The fundamental concept in Information Centric Networking (ICN) is to
provide the ability to access named information as a principal service
offered by the network, evolving the Internet from today?s host based
packet delivery towards directly retrieving information objects and
invoking services by name in a secure, reliable, scalable, and efficient
way. These architectural design efforts aim to address the challenges that
arise from the increasing demands for highly scalable content distribution,
from accessing cloud resources, from accelerated growth of mobile devices,
from wide deployment of Internet-of-things (IoT), and from the need to
secure the global Internet. Papers which reach out into related fields are
specifically encouraged.

(1) Use of ICN for both legacy problems and novel use cases, including but
not limited to:
? Content distribution
? Name-based access to cloud resources
? Device and content mobility
? IoT

(2) Network layer, mobility and architecture:
? Comparison of architectures, ICN styles and semantics
? Interdependency of namespace design, routing, and resource control
? ICN support for ad hoc and direct peer-to-peer communication
? ICN for high-speed networking

(3) Operations:
? Business and Economic models and their effects on deployability
? Management of ICN networks and systems
? Caching and its interaction with I/O performance
? Scalability analysis
? Traffic Engineering

(4) Security:
? Privacy, both generally and especially its interaction with caching
? Trust management and access control
? IoT-specific security considerations

(5) Application layer, evaluations and testbeds:
? APIs for transport, other higher-level abstractions, and their assessment
? Experience from implementation, testbeds, and tools
? Critical analysis of previous research in ICN, including reproducibility
studies
? Methodology and metrics

(6) Translational research:
? Deployments of ICN
? ICN for distributed computation, cloud-based services, database queries,
big data manipulation as well as ICN-mediated sensor/actuator control loops
? ICN-inspired applications and systems

(7) Implementation challenges and experiences
? Line speed caching
? Routing scalability
? Congestion control
? Zero conf ICN


Submission Guidelines
--------------------------------
Full-papers can be up to 10 pages in length, following the ACM SIGCOMM
format, and should convey results of mature research. Short-papers can be
up to 6 pages in length: This format is suitable for less mature
workshop-oriented work not qualifying for a full submission and for
thought-provoking position papers. Submissions exceeding the 6 pages length
will be considered as full-papers. Papers with doctoral students as first
authors are particularly encouraged. Note that in order to ensure adequate
citation of related work, extra pages of references are allowed (and
encouraged).

Submissions will be reviewed and evaluated on the basis of originality,
importance of contribution, soundness, evaluation, quality of presentation
and appropriate comparison to related work. The program committee as a
whole will make final decisions about which submissions to accept for
presentation at the conference. A ?best paper award? will be attributed
from the program committee to one among the accepted papers in each of the
Full paper and Short paper categories. The program committee may invite
authors of non-accepted papers present their work with a poster accompanied
by a 2-page extended abstract. Please note that ACM ICN 2017 also has a
specific call for posters, demos, tutorials, and panel sessions.

To submit papers to the ICN 2017 conference, please read carefully the
submission policies, the conflicts of interest, and the formatting
requirements specified here:
http://conferences.sigcomm.org/acm-icn/2017//submission.html

Organization Committee
--------------------------------
General Chairs:
Thomas C. Schmidt, HAW Hamburg, DE
Jan Seedorf, HFT Stuttgart, DE

TPC Chairs:
Dave Oran, US
Christian Tschudin, University of Basel, CH

Local Chairs:
Matthias W?hlisch, Freie Universit?t Berlin, DE
Mayutan Arumaithurai, Universitt G?ttingen, DE

Demo/Poster Chairs:
Alexander Afanasyev, UCLA, US
Jussi Kangasharju, University of Helsinki, FI

Travel Grant Chairs
J. J. Garcia-Luna-Aceves, UCSC/Parc, US
Jianping Wang, City University of Hong Kong, China

Publication Chair:
Atsushi Tagami, KDDI Labs, Japan

Publicity Chair:
Edith Ngai, Uppsala University, SE

Web Chair:
Christopher A. Wood, UCI, US

Steering Committee:
George C. Polyzos, Chair, AUEB, Greece
Giovanna Carofiglio, Cisco, FR
Dirk Kutscher, Huawei, DE
Luca Muscariello, Cisco, FR
B?rje Ohlman, Ericsson Research, SE
J?rg Ott, Technische Universit?t M?nchen, DE
Lixia Zhang, UCLA, US

Important Dates
--------------------------------
Paper Registration Deadline: May 1, 2017
Paper Submission Deadline: May 8, 2017
Acceptance Notification: July 18, 2017
Camera Ready Due: August 21, 2017
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170308/a88b5e5d/attachment.html>

From jlee700 at illinois.edu  Thu Mar  9 14:56:02 2017
From: jlee700 at illinois.edu (Lee, Jongdeog)
Date: Thu, 9 Mar 2017 22:56:02 +0000
Subject: [Ndn-interest] Secure Log-in mechanism in NDN
Message-ID: <BCBFBC0B008B2443A454A13CD91EBEDA2DC74BC2@CITESMBX6.ad.uillinois.edu>

Dear all,

  Hope all of you are doing fine. I have a question regarding NDN log-in mechanism.

  Given that we have producer and consumer model, what would be a secure (possibly standard) log-in mechanism? Or there is no such thing in NDN world by assuming that all producer and consumer have public-private key pairs?

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: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170309/f140e619/attachment.html>

From mayutan.arumaithurai at gmail.com  Tue Mar 14 09:55:44 2017
From: mayutan.arumaithurai at gmail.com (Mayutan A.)
Date: Tue, 14 Mar 2017 17:55:44 +0100
Subject: [Ndn-interest] ACM SIGCOMM 2017: Call for Posters,
 Demos and Industrial Demos
Message-ID: <CAADkTf0tDwTXb5Q2ojCXNo+aHfR-o-q+D2Gvw3EkRnWDg3qDTA@mail.gmail.com>

====================================================
Call for Posters and Demos
ACM SIGCOMM 2017

UCLA, Los Angeles, CA, USA on August 21-25, 2017

http://conferences.sigcomm.org/sigcomm/2017/cf-posters.html
====================================================

The SIGCOMM poster and demo sessions showcase works-in-progress in an
informal setting. Topics of interest are the same as research topics in the
SIGCOMM conference call for papers. We strongly encourage student and
industry submissions. The SIGCOMM 2017 Poster and Demo committee will
review all posters and demo proposals.

Please note that product-focused, as opposed to research-focused,
industrial demos may be more appropriately submitted to the SIGCOMM
Industrial Demo track.

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.
We will summarize accepted submissions in an editorial note in the SIGCOMM
newsletter, the Computer Communication Review (CCR). Students who are
submitting posters are highly encouraged to examine if they are eligible
for student travel grants.

Poster and Demo submissions may qualify for the Student Research
Competition, see http://conferences.sigcomm.org/sigcomm/2017/src.html.

Submission details:
- http://conferences.sigcomm.org/sigcomm/2017/cf-posters.html

Important dates:
- Submissions Deadline: May 17, 2017
- Notification of Acceptance: June 14, 2017

Chairs (posteranddemochairs17 at sigcomm.org):
- Matthias Waehlisch, Freie Universitaet Berlin, Germany.
- Jeff Burke, University of California, Los Angeles, USA.
- Nicholas Zhang, Huawei, HongKong.

====================================================
Call for Industrial Demos
ACM SIGCOMM 2017

UCLA, Los Angeles, CA, USA on August 21-25, 2017

http://conferences.sigcomm.org/sigcomm/2017/cf-industrial-demos.html
====================================================

The industrial demo sessions at SIGCOMM 2015 and 2016 had a great turnout
and positive feedback, so the Industrial Demos session will return for
SIGCOMM 2017. The industrial demo session showcases demos from industry in
the area of networking, networked systems, as well as new forms of network
intelligence and networked applications. The objective of this session is
to bring together industry and academia around demos of innovative and
cutting-edge networking technology and products.

Why Present Industrial Demos at SIGCOMM?

An industrial demo is an opportunity for companies to show industrial
leadership and innovative thinking. Presenting cutting edge industrial
technology will attract top academics to work on problems that are relevant
to industry and help push forward the frontier of industrial knowledge. The
industrial demo session is also a great recruiting opportunity. SIGCOMM
attracts students from the most selective universities around the world.

Submission details:
- http://conferences.sigcomm.org/sigcomm/2017/cf-industrial-demos.html

Important dates:
- Submissions Deadline: May 26, 2017
- Notification of Acceptance: June 19, 2017

Chairs (industrialdemochairs17 at sigcomm.org):
- David Meyer, University of Oregon/Brocade, USA.
- Puneet Sharma, Hewlett Packard Labs, USA.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170314/4d6f4f6c/attachment-0001.html>

From s.h.ahmed at ieee.org  Fri Mar 17 09:27:45 2017
From: s.h.ahmed at ieee.org (Syed Hassan Ahmed)
Date: Sat, 18 Mar 2017 01:27:45 +0900
Subject: [Ndn-interest] IEEE Commag FT: Call for Submissions
Message-ID: <CAJeX4qd8uYYbuNv8azHOKPxotNgQRrnzwz3ud9YpVTrZOE_rLQ@mail.gmail.com>

Dear all ICN Researchers,

Through this email, I would like to invite submissions to our following
Feature Topic with IEEE Communications Magazine:

http://www.comsoc.org/commag/cfp/imminent-communication-technologies-smart-communities

The role of ICN in Building Smart Communities can be a tentative research
scope for this FT.

Interested authors can contact me or submit their work according to the
guidelines.

Best Regards,
Syed Hassan Ahmed,
Kyungpook National University,
Daegu, Republic of Korea.
https://sites.google.com/site/shahmedknu/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170318/44534cf4/attachment.html>

From shijunxiao at email.arizona.EDU  Sun Mar 19 05:19:59 2017
From: shijunxiao at email.arizona.EDU (Junxiao Shi)
Date: Sun, 19 Mar 2017 05:19:59 -0700
Subject: [Ndn-interest] Secure Log-in mechanism in NDN
In-Reply-To: <BCBFBC0B008B2443A454A13CD91EBEDA2DC74BC2@CITESMBX6.ad.uillinois.edu>
References: <BCBFBC0B008B2443A454A13CD91EBEDA2DC74BC2@CITESMBX6.ad.uillinois.edu>
Message-ID: <CAOFH+OYrKEY3M081G=QNXhdQh5apY-PMqLSGBBAh-8eZ6Jtzyg@mail.gmail.com>

Hi Jongdeog

First of all, any NDN application, including ndnping, has a "producer and
consumer model". I guess you mean "server and client model". The client can
download from the server, and can upload to the server. During the upload,
the client would act as a producer while the server acts as a consumer.

In web technology, "log-in" means session management. A Windows 7
era example: Alice wants to access her Hotmail mailbox. She visits
hotmail.com, which redirects her to Windows Live ID sign-in page. Over
there, she either types her username and password, or selects a smartcard
via Windows CardSpace. Windows Live ID issues a token (as a browser cookie)
to Alice, which is accepted by hotmail.com and Alice is able to access her
mailbox. When she finishes, pressing sign-out revokes the token so that
nobody else can use it.

The session token / session cookie in web technology is equivalent to
certificate in NDN.
The NDN equivalent of the above, assuming using smartcard, is: Alice issues
a certificate for her Hotmail session and have it signed by her smartcard,
she can then access Hotmail with this certificate. Session ends when the
certificate expires.
The case with username+password is more complicated in NDN, but still
doable: Alice generates a key pair, and sends a certificate request along
with the username+password to Windows Live ID sign-in service (the message
is encrypted by Windows Live ID site's public key). After obtaining a
certificate from Windows Live ID, Alice can issue herself a Hotmail session
certificate.

Yours, Junxiao

On Thu, Mar 9, 2017 at 3:56 PM, Lee, Jongdeog <jlee700 at illinois.edu> wrote:

> Dear all,
>
>   Hope all of you are doing fine. I have a question regarding NDN log-in
> mechanism.
>
>   Given that we have producer and consumer model, what would be a secure
> (possibly standard) log-in mechanism? Or there is no such thing in NDN
> world by assuming that all producer and consumer have public-private key
> pairs?
>
> Best wishes,
> Jongdeog Lee (JD)
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170319/8a82df68/attachment.html>

From lanwang at memphis.edu  Sun Mar 19 12:43:30 2017
From: lanwang at memphis.edu (Lan Wang (lanwang))
Date: Sun, 19 Mar 2017 19:43:30 +0000
Subject: [Ndn-interest] Secure Log-in mechanism in NDN
In-Reply-To: <CAOFH+OYrKEY3M081G=QNXhdQh5apY-PMqLSGBBAh-8eZ6Jtzyg@mail.gmail.com>
References: <BCBFBC0B008B2443A454A13CD91EBEDA2DC74BC2@CITESMBX6.ad.uillinois.edu>
	<CAOFH+OYrKEY3M081G=QNXhdQh5apY-PMqLSGBBAh-8eZ6Jtzyg@mail.gmail.com>
Message-ID: <198DC159-E532-4AB5-BB8D-38BE79689215@memphis.edu>

Jongdeog?s question is about access control.  Rather than emulating how the current solutions work, an NDN producer can encrypt the data and distribute the data decryption key to the user (using the user?s public key to encrypt the data decryption key).  See "Name-Based Access Control." Y. Yu, A. Afanasyev, L. Zhang.
NDN, Technical Report NDN-0034. https://named-data.net/publications/techreports/ndn-0034-2-nac/

Lan

On Mar 19, 2017, at 7:19 AM, Junxiao Shi <shijunxiao at email.arizona.edu<mailto:shijunxiao at email.arizona.edu>> wrote:

Hi Jongdeog

First of all, any NDN application, including ndnping, has a "producer and consumer model". I guess you mean "server and client model". The client can download from the server, and can upload to the server. During the upload, the client would act as a producer while the server acts as a consumer.

In web technology, "log-in" means session management. A Windows 7 era example: Alice wants to access her Hotmail mailbox. She visits hotmail.com<http://hotmail.com/>, which redirects her to Windows Live ID sign-in page. Over there, she either types her username and password, or selects a smartcard via Windows CardSpace. Windows Live ID issues a token (as a browser cookie) to Alice, which is accepted by hotmail.com<http://hotmail.com/> and Alice is able to access her mailbox. When she finishes, pressing sign-out revokes the token so that nobody else can use it.

The session token / session cookie in web technology is equivalent to certificate in NDN.
The NDN equivalent of the above, assuming using smartcard, is: Alice issues a certificate for her Hotmail session and have it signed by her smartcard, she can then access Hotmail with this certificate. Session ends when the certificate expires.
The case with username+password is more complicated in NDN, but still doable: Alice generates a key pair, and sends a certificate request along with the username+password to Windows Live ID sign-in service (the message is encrypted by Windows Live ID site's public key). After obtaining a certificate from Windows Live ID, Alice can issue herself a Hotmail session certificate.

Yours, Junxiao

On Thu, Mar 9, 2017 at 3:56 PM, Lee, Jongdeog <jlee700 at illinois.edu<mailto:jlee700 at illinois.edu>> wrote:
Dear all,

  Hope all of you are doing fine. I have a question regarding NDN log-in mechanism.

  Given that we have producer and consumer model, what would be a secure (possibly standard) log-in mechanism? Or there is no such thing in NDN world by assuming that all producer and consumer have public-private key pairs?

Best wishes,
Jongdeog Lee (JD)



_______________________________________________
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu<mailto:Ndn-interest at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest

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

From gts at ics.uci.EDU  Sun Mar 19 12:54:37 2017
From: gts at ics.uci.EDU (GTS)
Date: Sun, 19 Mar 2017 12:54:37 -0700
Subject: [Ndn-interest] Secure Log-in mechanism in NDN
In-Reply-To: <198DC159-E532-4AB5-BB8D-38BE79689215@memphis.edu>
References: <BCBFBC0B008B2443A454A13CD91EBEDA2DC74BC2@CITESMBX6.ad.uillinois.edu>
	<CAOFH+OYrKEY3M081G=QNXhdQh5apY-PMqLSGBBAh-8eZ6Jtzyg@mail.gmail.com>
	<198DC159-E532-4AB5-BB8D-38BE79689215@memphis.edu>
Message-ID: <007fe5a2-0426-654f-9367-eafe4950268b@ics.uci.edu>

The same general approach was explored earlier in this paper (in the 
context of CCNx, but applicable to NDN):

J. Kurihara, C. A. Wood, and E. Uzun,
An Encryption-Based Access Control Framework for Content-Centric 
Networking <http://sprout.ics.uci.edu/projects/ndn/papers/ccnac15.pdf>,
/in IFIP Networking/, Toulouse, France, 2015.

Cheers,
Gene Tsudik



On 3/19/17 12:43 PM, Lan Wang (lanwang) wrote:
> Jongdeog?s question is about access control.  Rather than emulating 
> how the current solutions work, an NDN producer can encrypt the data 
> and distribute the data decryption key to the user (using the user?s 
> public key to encrypt the data decryption key).  See "Name-Based 
> Access Control." Y. Yu, A. Afanasyev, L. Zhang.
> NDN, Technical Report NDN-0034. 
> https://named-data.net/publications/techreports/ndn-0034-2-nac/
>
> Lan
>
>> On Mar 19, 2017, at 7:19 AM, Junxiao Shi 
>> <shijunxiao at email.arizona.edu <mailto:shijunxiao at email.arizona.edu>> 
>> wrote:
>>
>> Hi Jongdeog
>>
>> First of all, any NDN application, including ndnping, has a "producer 
>> and consumer model". I guess you mean "server and client model". The 
>> client can download from the server, and can upload to the server. 
>> During the upload, the client would act as a producer while the 
>> server acts as a consumer.
>>
>> In web technology, "log-in" means session management. A Windows 7 
>> era example: Alice wants to access her Hotmail mailbox. She visits 
>> hotmail.com <http://hotmail.com/>, which redirects her to Windows 
>> Live ID sign-in page. Over there, she either types her username and 
>> password, or selects a smartcard via Windows CardSpace. Windows Live 
>> ID issues a token (as a browser cookie) to Alice, which is accepted 
>> by hotmail.com <http://hotmail.com/> and Alice is able to access her 
>> mailbox. When she finishes, pressing sign-out revokes the token so 
>> that nobody else can use it.
>>
>> The session token / session cookie in web technology is equivalent to 
>> certificate in NDN.
>> The NDN equivalent of the above, assuming using smartcard, is: Alice 
>> issues a certificate for her Hotmail session and have it signed by 
>> her smartcard, she can then access Hotmail with this certificate. 
>> Session ends when the certificate expires.
>> The case with username+password is more complicated in NDN, but still 
>> doable: Alice generates a key pair, and sends a certificate request 
>> along with the username+password to Windows Live ID sign-in service 
>> (the message is encrypted by Windows Live ID site's public key). 
>> After obtaining a certificate from Windows Live ID, Alice can issue 
>> herself a Hotmail session certificate.
>>
>> Yours, Junxiao
>>
>> On Thu, Mar 9, 2017 at 3:56 PM, Lee, Jongdeog <jlee700 at illinois.edu 
>> <mailto:jlee700 at illinois.edu>> wrote:
>>
>>     Dear all,
>>
>>       Hope all of you are doing fine. I have a question regarding NDN
>>     log-in mechanism.
>>
>>       Given that we have producer and consumer model, what would be a
>>     secure (possibly standard) log-in mechanism? Or there is no such
>>     thing in NDN world by assuming that all producer and consumer
>>     have public-private key pairs?
>>
>>     Best wishes,
>>     Jongdeog Lee (JD)
>>
>>
>>
>> _______________________________________________
>> Ndn-interest mailing list
>> Ndn-interest at lists.cs.ucla.edu <mailto:Ndn-interest at lists.cs.ucla.edu>
>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>
>
>
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest

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

From david.cittadini at icloud.com  Sun Mar 19 23:20:54 2017
From: david.cittadini at icloud.com (David Cittadini)
Date: Mon, 20 Mar 2017 07:20:54 +0100
Subject: [Ndn-interest] Cisco CCN and NDN
Message-ID: <486AFC04-D8CE-40C1-BAED-0FC16C301AD5@icloud.com>

I have a few ?beginner? questions:

1.	How does the new Cisco CCN announcement affect the work being done on the NDN.

2.	Is there a way for end-user application developers to simply test/try the NDN or does one have to setup a complete NDN system and formally join the ?testbed?.  I am looking for a way to focus on the high-level application side without having to master/deploy the complete NDN infrastructure.

Thanks :)

From mesarpe at gmail.com  Mon Mar 20 06:11:48 2017
From: mesarpe at gmail.com (=?UTF-8?Q?C=C3=A9sar_A=2E_Bernardini?=)
Date: Mon, 20 Mar 2017 14:11:48 +0100
Subject: [Ndn-interest] Cisco CCN and NDN
In-Reply-To: <486AFC04-D8CE-40C1-BAED-0FC16C301AD5@icloud.com>
References: <486AFC04-D8CE-40C1-BAED-0FC16C301AD5@icloud.com>
Message-ID: <CAO9+PG85=2GMEUmJRL31Rb=u3JKmVC3-rqiiViqaJOBwwoJR8A@mail.gmail.com>

Hi David,

I cannot answer your question #1.

For the question #2, the normal approach is to simply install the daemon
ndnd if you are using NDN, or the Athena forwarder if you are using CCNx.
As Cisco bought from PARC the CCNx implementation, I guess for Cisco it is
the same. With ndnd or Athena Forwarder, you can simply start playing with
a simple node. I strongly suggest you to install it in a VM and then
replicate to create a network. Once you are an expert, you can search how
to integrate your NDN/CCN network to the NDN Infrastructure. However, as it
is an experimental configuration, I'd suggest you to stay with your VMs.

Bests,

2017-03-20 7:20 GMT+01:00 David Cittadini <david.cittadini at icloud.com>:

> I have a few ?beginner? questions:
>
> 1.      How does the new Cisco CCN announcement affect the work being done
> on the NDN.
>
> 2.      Is there a way for end-user application developers to simply
> test/try the NDN or does one have to setup a complete NDN system and
> formally join the ?testbed?.  I am looking for a way to focus on the
> high-level application side without having to master/deploy the complete
> NDN infrastructure.
>
> Thanks :)
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170320/1a7f04e9/attachment.html>

From lanwang at memphis.edu  Mon Mar 20 08:35:18 2017
From: lanwang at memphis.edu (Lan Wang (lanwang))
Date: Mon, 20 Mar 2017 15:35:18 +0000
Subject: [Ndn-interest] Cisco CCN and NDN
In-Reply-To: <486AFC04-D8CE-40C1-BAED-0FC16C301AD5@icloud.com>
References: <486AFC04-D8CE-40C1-BAED-0FC16C301AD5@icloud.com>
Message-ID: <AF5F282C-EBAE-4E0C-9785-23AE2E17BAAC@memphis.edu>



On Mar 20, 2017, at 1:20 AM, David Cittadini <david.cittadini at icloud.com<mailto:david.cittadini at icloud.com>> wrote:

I have a few ?beginner? questions:

1. How does the new Cisco CCN announcement affect the work being done on the NDN.

Luca Muscariello from Cisco will talk about this at the NDNcomm meeting on March 23 in the 13:30-14:30 panel  (http://www.caida.org/workshops/ndn/1703/).  NDNcomm will be streamed online in case you cannot attend physically.

23rd -http://mediasite.memphis.edu/Mediasite/Play/b946b7085dea4573aba78d0425bd5fd91d
24th -http://mediasite.memphis.edu/Mediasite/Play/cd3596a0b235492cbc049754b8f037d71d

2. Is there a way for end-user application developers to simply test/try the NDN or does one have to setup a complete NDN system and formally join the ?testbed?.  I am looking for a way to focus on the high-level application side without having to master/deploy the complete NDN infrastructure.

Jeff Burke and Jeff Thompson can answer this question.  They have developed some tools that may help applications to do this.

Lan

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

From lanwang at memphis.edu  Mon Mar 20 10:19:28 2017
From: lanwang at memphis.edu (Lan Wang (lanwang))
Date: Mon, 20 Mar 2017 17:19:28 +0000
Subject: [Ndn-interest] Cisco CCN and NDN
In-Reply-To: <AF5F282C-EBAE-4E0C-9785-23AE2E17BAAC@memphis.edu>
References: <486AFC04-D8CE-40C1-BAED-0FC16C301AD5@icloud.com>
	<AF5F282C-EBAE-4E0C-9785-23AE2E17BAAC@memphis.edu>
Message-ID: <BB977078-BB62-469F-99ED-BCDF352B6FBE@memphis.edu>

Just want to correct that the panel mentioned below will be on March 24.

Lan

On Mar 20, 2017, at 10:35 AM, Lan Wang <lanwang at memphis.edu<mailto:lanwang at memphis.edu>> wrote:



On Mar 20, 2017, at 1:20 AM, David Cittadini <david.cittadini at icloud.com<mailto:david.cittadini at icloud.com>> wrote:

I have a few ?beginner? questions:

1. How does the new Cisco CCN announcement affect the work being done on the NDN.

Luca Muscariello from Cisco will talk about this at the NDNcomm meeting on March 23 in the 13:30-14:30 panel  (http://www.caida.org/workshops/ndn/1703/).  NDNcomm will be streamed online in case you cannot attend physically.

23rd -http://mediasite.memphis.edu/Mediasite/Play/b946b7085dea4573aba78d0425bd5fd91d
24th -http://mediasite.memphis.edu/Mediasite/Play/cd3596a0b235492cbc049754b8f037d71d

2. Is there a way for end-user application developers to simply test/try the NDN or does one have to setup a complete NDN system and formally join the ?testbed?.  I am looking for a way to focus on the high-level application side without having to master/deploy the complete NDN infrastructure.

Jeff Burke and Jeff Thompson can answer this question.  They have developed some tools that may help applications to do this.

Lan


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

From jefft0 at remap.UCLA.EDU  Mon Mar 20 10:23:35 2017
From: jefft0 at remap.UCLA.EDU (Thompson, Jeff)
Date: Mon, 20 Mar 2017 17:23:35 +0000
Subject: [Ndn-interest]  Cisco CCN and NDN
In-Reply-To: <D4F54EF9.3AC03%jefft0@remap.ucla.edu>
References: <486AFC04-D8CE-40C1-BAED-0FC16C301AD5@icloud.com>
	<D4F54EF9.3AC03%jefft0@remap.ucla.edu>
Message-ID: <D4F55E06.3AC18%jefft0@remap.ucla.edu>

Hi David,

We just released a new ?NDN Platform? in preparation for NDNcomm.
https://named-data.net/codebase/platform/

This includes the NFD forwarder. As mentioned, you can install this on a standalone machine (without needing the testbed) or you can set up multiple machines each with NFD and routes between them. There are example applications in multiple languages. For example if you want Python you can download PyNDN2. If you want to simulate more sophisticated network configurations, you can use ndnSIM or Mini-NDN.

Note that you can send interests to the NDN testbed and get response Data packets without needing to ?join? it. But if you do get to the point where you want to register to receive Interests (and serve content), there are ways to do that.

Thanks,
- Jeff T

On 2017/3/19, 23:20:54, "Ndn-interest on behalf of David Cittadini" <ndn-interest-bounces at lists.cs.ucla.edu<mailto:ndn-interest-bounces at lists.cs.ucla.edu> on behalf of david.cittadini at icloud.com<mailto:david.cittadini at icloud.com>> wrote:

I have a few ?beginner? questions:

1. How does the new Cisco CCN announcement affect the work being done on the NDN.

2. Is there a way for end-user application developers to simply test/try the NDN or does one have to setup a complete NDN system and formally join the ?testbed?.  I am looking for a way to focus on the high-level application side without having to master/deploy the complete NDN infrastructure.

Thanks :)
_______________________________________________
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu<mailto:Ndn-interest at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest

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

From agawande at memphis.edu  Mon Mar 20 13:45:28 2017
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Mon, 20 Mar 2017 20:45:28 +0000
Subject: [Ndn-interest] NLSR 0.3.2 release
Message-ID: <DM5PR04MB0842A10424FD25DB7006B151D93A0@DM5PR04MB0842.namprd04.prod.outlook.com>

Hi all,

We are happy to announce the release of version 0.3.2 of Named-data Link
State Routing Protocol (NLSR).

This is a very minor release aimed at fixing the security section of
the configuration file without which NLSR fails to validate LSA data.
This bug was introduced in the 0.3.1 release.

Detailed release notes can be found at:
http://named-data.net/doc/NLSR/0.3.2/RELEASE-NOTES.html

More information about NLSR, tutorials, installation and configuration
guides, and other useful information can be found at:
http://named-data.net/doc/NLSR/0.3.2/

* * *
NLSR Developers and Contributors:
Vince Lehman, A K M Mahmudul Hoque, Adam Alyyan, Syed Obaid Amin,
Muktadir Chowdhury, Ashlesh Gawande, Minsheng Zhang, Nicholas Gordon,
Laqin Fan, Lan Wang, Alexander Afanasyev, Spyridon Mastorakis, Jiewen
Tan, Yingdi Yu, Lixia Zhang, Junxiao Shi, Eric Newberry, Beichuan Zhang

Thanks
Ashlesh

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

From malhowaidi at gmail.com  Tue Mar 21 14:26:33 2017
From: malhowaidi at gmail.com (Mohammad Alhowaidi)
Date: Tue, 21 Mar 2017 16:26:33 -0500
Subject: [Ndn-interest] Converting Files into NDN format
Message-ID: <CAOYiq136husMto3fAxQFuHWjMMNgOEmVQ9fTCvq7uutSqQsWDg@mail.gmail.com>

Dear all,

I have many files which I need to convert them into NDN packets before the
interest arrive in order to reduce the delay. Is there any existing way
which do that?

Thanks,
Mohammad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170321/3871bc72/attachment.html>

From aa at CS.UCLA.EDU  Tue Mar 21 16:14:58 2017
From: aa at CS.UCLA.EDU (Alex Afanasyev)
Date: Tue, 21 Mar 2017 18:14:58 -0500
Subject: [Ndn-interest] Cisco CCN and NDN
In-Reply-To: <486AFC04-D8CE-40C1-BAED-0FC16C301AD5@icloud.com>
References: <486AFC04-D8CE-40C1-BAED-0FC16C301AD5@icloud.com>
Message-ID: <1B6C6E38-3B23-4512-AD92-D4ED1DF1896E@cs.ucla.edu>


> On Mar 20, 2017, at 1:20 AM, David Cittadini <david.cittadini at icloud.com> wrote:
> 
> I have a few ?beginner? questions:
> 
> 1.	How does the new Cisco CCN announcement affect the work being done on the NDN.

I don't see any impact, except a positive one.

> 2.	Is there a way for end-user application developers to simply test/try the NDN or does one have to setup a complete NDN system and formally join the ?testbed?.  I am looking for a way to focus on the high-level application side without having to master/deploy the complete NDN infrastructure.

I would like to state my opinion here that doesn't directly answer your question.  NDN's real "edge" is in infrastructure-less environments, such as IoT, vehicular networking, disaster recovery scenarios, etc.  Therefore, to really start with NDN you only need an NDN stack on the node that can be added in a few simple ways:
- if you are on Android, you can simply download NDN app that bundles, runs, and enables seamless NDN over Wifi Direct (https://play.google.com/store/apps/details?id=net.named_data.nfd <https://play.google.com/store/apps/details?id=net.named_data.nfd>)
- if you are on macOS, you can download NDN Control Center app for the same (https://named-data.net/codebase/applications/ndn-control-center/ <https://named-data.net/codebase/applications/ndn-control-center/>)
- if you are on Linux (Ubuntu), just install nfd and related packages from our PPA (http://named-data.net/doc/NFD/current/INSTALL.html#install-nfd-using-the-ndn-ppa-repository-on-ubuntu-linux <http://named-data.net/doc/NFD/current/INSTALL.html#install-nfd-using-the-ndn-ppa-repository-on-ubuntu-linux>)
- if you are interested working with microcontrollers (constrained memory and CPU), you can start with NDN-RIOT (https://github.com/named-data-iot/ndn-riot <https://github.com/named-data-iot/ndn-riot>)
- if you're playing with Raspberry Pi-like devices, there is NDN-Pi image (https://github.com/remap/ndn-pi/releases <https://github.com/remap/ndn-pi/releases>) and you would find this page very useful https://redmine.named-data.net/projects/ndn-embedded/wiki <https://redmine.named-data.net/projects/ndn-embedded/wiki> 

If you want experiment including infrastructure, you can establish connectivity with NDN testbed (it is open for experimentation and joining) or deploy nodes on your own.

--
Alex

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

From aa at CS.UCLA.EDU  Tue Mar 21 16:16:21 2017
From: aa at CS.UCLA.EDU (Alex Afanasyev)
Date: Tue, 21 Mar 2017 18:16:21 -0500
Subject: [Ndn-interest] Converting Files into NDN format
In-Reply-To: <CAOYiq136husMto3fAxQFuHWjMMNgOEmVQ9fTCvq7uutSqQsWDg@mail.gmail.com>
References: <CAOYiq136husMto3fAxQFuHWjMMNgOEmVQ9fTCvq7uutSqQsWDg@mail.gmail.com>
Message-ID: <F8A66E39-97A0-45F4-9FB9-C2F45FF37F2F@cs.ucla.edu>

You may be interested in NDNFS work (code: https://github.com/named-data/NDNFS <https://github.com/named-data/NDNFS>, technical report: https://named-data.net/publications/techreports/ndn-tr-27-ndnfs/ <https://named-data.net/publications/techreports/ndn-tr-27-ndnfs/>)

--
Alex

> On Mar 21, 2017, at 4:26 PM, Mohammad Alhowaidi <malhowaidi at gmail.com> wrote:
> 
> Dear all,
> 
> I have many files which I need to convert them into NDN packets before the interest arrive in order to reduce the delay. Is there any existing way which do that? 
> 
> Thanks,
> Mohammad

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

From philipp.moll at itec.aau.at  Tue Mar 21 23:55:24 2017
From: philipp.moll at itec.aau.at (Philipp Moll)
Date: Wed, 22 Mar 2017 07:55:24 +0100
Subject: [Ndn-interest] Cisco CCN and NDN
In-Reply-To: <1B6C6E38-3B23-4512-AD92-D4ED1DF1896E@cs.ucla.edu>
References: <486AFC04-D8CE-40C1-BAED-0FC16C301AD5@icloud.com>
	<1B6C6E38-3B23-4512-AD92-D4ED1DF1896E@cs.ucla.edu>
Message-ID: <6db0d0ff-feaf-51d2-0304-20ab2cda3099@itec.aau.at>

Hi David,

2. If you are interested in testing your applications on a local testbed 
you can also have a look on the "Low-cost NDN testbed" from my 
colleagues. ( http://icn.itec.aau.at/ndn-network/guide/ , 
http://ieeexplore.ieee.org/document/7565256/ )

Best regards,
Philipp Moll

On 22/03/17 00:14, Alex Afanasyev wrote:
>
>> On Mar 20, 2017, at 1:20 AM, David Cittadini 
>> <david.cittadini at icloud.com <mailto:david.cittadini at icloud.com>> wrote:
>>
>> I have a few ?beginner? questions:
>>
>> 1.How does the new Cisco CCN announcement affect the work being done 
>> on the NDN.
>
> I don't see any impact, except a positive one.
>
>> 2.Is there a way for end-user application developers to simply 
>> test/try the NDN or does one have to setup a complete NDN system and 
>> formally join the ?testbed?.  I am looking for a way to focus on the 
>> high-level application side without having to master/deploy the 
>> complete NDN infrastructure.
>
> I would like to state my opinion here that doesn't directly answer 
> your question.  NDN's real "edge" is in infrastructure-less 
> environments, such as IoT, vehicular networking, disaster recovery 
> scenarios, etc.  Therefore, to really start with NDN you only need an 
> NDN stack on the node that can be added in a few simple ways:
> - if you are on Android, you can simply download NDN app that bundles, 
> runs, and enables seamless NDN over Wifi Direct 
> (https://play.google.com/store/apps/details?id=net.named_data.nfd)
> - if you are on macOS, you can download NDN Control Center app for the 
> same (https://named-data.net/codebase/applications/ndn-control-center/)
> - if you are on Linux (Ubuntu), just install nfd and related packages 
> from our PPA 
> (http://named-data.net/doc/NFD/current/INSTALL.html#install-nfd-using-the-ndn-ppa-repository-on-ubuntu-linux)
> - if you are interested working with microcontrollers (constrained 
> memory and CPU), you can start with NDN-RIOT 
> (https://github.com/named-data-iot/ndn-riot)
> - if you're playing with Raspberry Pi-like devices, there is NDN-Pi 
> image (https://github.com/remap/ndn-pi/releases) and you would find 
> this page very useful 
> https://redmine.named-data.net/projects/ndn-embedded/wiki
>
> If you want experiment including infrastructure, you can establish 
> connectivity with NDN testbed (it is open for experimentation and 
> joining) or deploy nodes on your own.
>
> --
> Alex
>
>
>
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest

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

From malhowaidi at gmail.com  Wed Mar 22 17:17:18 2017
From: malhowaidi at gmail.com (Mohammad Alhowaidi)
Date: Wed, 22 Mar 2017 19:17:18 -0500
Subject: [Ndn-interest] Converting Files into NDN format
In-Reply-To: <F8A66E39-97A0-45F4-9FB9-C2F45FF37F2F@cs.ucla.edu>
References: <CAOYiq136husMto3fAxQFuHWjMMNgOEmVQ9fTCvq7uutSqQsWDg@mail.gmail.com>
	<F8A66E39-97A0-45F4-9FB9-C2F45FF37F2F@cs.ucla.edu>
Message-ID: <CAOYiq131+rhj1BsgDnhBVKtb5NpePWOocz0SWRz_wZBO3DLjJw@mail.gmail.com>

Thank you for your reply but I am unable to install NDNFS due to the
following error:

Checking MongoDB                         : Cannot find MongoDB library
(complete log in /home/ubuntu/NDNFS/build/config.log)

and when I check the config.log it shows the following error when it tries
to compile the test file

err: /usr/bin/ld: /usr/local/lib/libmongoclient.a(spin_lock.o): undefined
reference to symbol 'pthread_yield@@GLIBC_2.2.5'
//lib/x86_64-linux-gnu/libpthread.so.0: error adding symbols: DSO missing
from command line
collect2: error: ld returned 1 exit status

I guess the error happens due to missing *-lpthread* flag.

Can you please tell how to fix the error?

Thanks,
Mohammad


On Tue, Mar 21, 2017 at 6:16 PM, Alex Afanasyev <aa at cs.ucla.edu> wrote:

> You may be interested in NDNFS work (code: https://github.com/
> named-data/NDNFS, technical report: https://named-data.
> net/publications/techreports/ndn-tr-27-ndnfs/)
>
> --
> Alex
>
> On Mar 21, 2017, at 4:26 PM, Mohammad Alhowaidi <malhowaidi at gmail.com>
> wrote:
>
> Dear all,
>
> I have many files which I need to convert them into NDN packets before the
> interest arrive in order to reduce the delay. Is there any existing way
> which do that?
>
> Thanks,
> Mohammad
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170322/e19b71e1/attachment-0001.html>

From zpymyyn at gmail.com  Thu Mar 23 03:06:28 2017
From: zpymyyn at gmail.com (Pengyuan Zhou)
Date: Thu, 23 Mar 2017 11:06:28 +0100
Subject: [Ndn-interest] NameSpace
Message-ID: <A4297EFC-F3A6-43AF-8782-5EC4E7F3E8FF@gmail.com>

Hi all,

I?m curious if including some related info into the namespace of Interest packet and Data packet would help, or at least not harmful.

Such as author?s name, generated timestamp etc.

Thanks.

Best,
Pengyuan 

University of Helsinki

From lanwang at memphis.edu  Thu Mar 23 05:37:34 2017
From: lanwang at memphis.edu (Lan Wang (lanwang))
Date: Thu, 23 Mar 2017 12:37:34 +0000
Subject: [Ndn-interest] NDNcomm 2017 live streaming
Message-ID: <B119FE2C-FED2-499A-B5DE-CABC3F6C7FF5@memphis.edu>

Hi all,

Here?re the NDNcomm (NDN Community Meeting) 2017 live streams for today and tomorrow (starting at 8:30am central):

3/23: http://mediasite.memphis.edu/Mediasite/Play/b946b7085dea4573aba78d0425bd5fd91d

3/24: http://mediasite.memphis.edu/Mediasite/Play/cd3596a0b235492cbc049754b8f037d71d
 
Thanks,

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
***********************************************





From i.psaras at ucl.ac.uk  Sun Mar 26 13:49:43 2017
From: i.psaras at ucl.ac.uk (Psaras, Ioannis)
Date: Sun, 26 Mar 2017 20:49:43 +0000
Subject: [Ndn-interest] NameSpace
In-Reply-To: <A4297EFC-F3A6-43AF-8782-5EC4E7F3E8FF@gmail.com>
References: <A4297EFC-F3A6-43AF-8782-5EC4E7F3E8FF@gmail.com>
Message-ID: <DC5B5FA7-20D2-4B8B-873A-46367432C9BF@live.ucl.ac.uk>

Hi Pengyuan,

I believe the namespace can be used to include some useful information to help the network act accordingly on the data (especially in mobile environments).

We?ve got the following three (admittedly rather preliminary) works, that enhance, or rather extend the namespace with extra information. In most cases, the extra info comes in terms of metadata, or tags.

- Keyword-Based Mobile Application Sharing, ACM MobiArch 2016: https://www.ee.ucl.ac.uk/~uceeips/files/kebapp-mobiarch16.pdf

- Name-based replication priorities in disaster cases, NOMEN 2014: https://www.ee.ucl.ac.uk/~uceeips/files/nrep-nom14.pdf

- Information Exposure through named content, Q-ICN 2014: https://www.ee.ucl.ac.uk/comit-project/files/infoexp-qicn14.pdf

I suspect that timestamped information would be especially useful in IoT scenarios.

Best regards,
Yiannis.

On 23 Mar 2017, at 10:06, Pengyuan Zhou <zpymyyn at gmail.com> wrote:

> Hi all,
> 
> I?m curious if including some related info into the namespace of Interest packet and Data packet would help, or at least not harmful.
> 
> Such as author?s name, generated timestamp etc.
> 
> Thanks.
> 
> Best,
> Pengyuan 
> 
> University of Helsinki
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest



From zpymyyn at gmail.com  Sun Mar 26 14:59:39 2017
From: zpymyyn at gmail.com (Pengyuan Zhou)
Date: Sun, 26 Mar 2017 23:59:39 +0200
Subject: [Ndn-interest] NameSpace
In-Reply-To: <DC5B5FA7-20D2-4B8B-873A-46367432C9BF@live.ucl.ac.uk>
References: <A4297EFC-F3A6-43AF-8782-5EC4E7F3E8FF@gmail.com>
	<DC5B5FA7-20D2-4B8B-873A-46367432C9BF@live.ucl.ac.uk>
Message-ID: <24C44BFC-0F20-4558-A607-4C739B9C7FEB@gmail.com>

Hi Ioannis,

Thanks for replying.

Yes, as you said, I think the explicit naming feature of ICN, has a potentiality to introduce more built in features into network.

Such as your previous work and IoT with timestamps as mentioned.

To do that, I think including more info into namespace, packets with a standardised flexible structure is necessary.

Thanks.

Best,
Pengyuan


> On 26 Mar 2017, at 22:49, Psaras, Ioannis <i.psaras at ucl.ac.uk> wrote:
> 
> Hi Pengyuan,
> 
> I believe the namespace can be used to include some useful information to help the network act accordingly on the data (especially in mobile environments).
> 
> We?ve got the following three (admittedly rather preliminary) works, that enhance, or rather extend the namespace with extra information. In most cases, the extra info comes in terms of metadata, or tags.
> 
> - Keyword-Based Mobile Application Sharing, ACM MobiArch 2016: https://www.ee.ucl.ac.uk/~uceeips/files/kebapp-mobiarch16.pdf
> 
> - Name-based replication priorities in disaster cases, NOMEN 2014: https://www.ee.ucl.ac.uk/~uceeips/files/nrep-nom14.pdf
> 
> - Information Exposure through named content, Q-ICN 2014: https://www.ee.ucl.ac.uk/comit-project/files/infoexp-qicn14.pdf
> 
> I suspect that timestamped information would be especially useful in IoT scenarios.
> 
> Best regards,
> Yiannis.
> 
> On 23 Mar 2017, at 10:06, Pengyuan Zhou <zpymyyn at gmail.com> wrote:
> 
>> Hi all,
>> 
>> I?m curious if including some related info into the namespace of Interest packet and Data packet would help, or at least not harmful.
>> 
>> Such as author?s name, generated timestamp etc.
>> 
>> Thanks.
>> 
>> Best,
>> Pengyuan 
>> 
>> University of Helsinki
>> _______________________________________________
>> Ndn-interest mailing list
>> Ndn-interest at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
> 



From malhowaidi at gmail.com  Tue Mar 28 11:02:17 2017
From: malhowaidi at gmail.com (Mohammad Alhowaidi)
Date: Tue, 28 Mar 2017 13:02:17 -0500
Subject: [Ndn-interest] NDN packet size
Message-ID: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>

Hello,

I was wondering how to increase NDN packet size, instead of using 8K? and
is there any limitation from increasing it?

Thanks,
Mohammad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170328/06f0568b/attachment.html>

From mastorakis at CS.UCLA.EDU  Tue Mar 28 11:03:54 2017
From: mastorakis at CS.UCLA.EDU (Spyridon (Spyros) Mastorakis)
Date: Tue, 28 Mar 2017 11:03:54 -0700
Subject: [Ndn-interest] NDN packet size
In-Reply-To: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
References: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
Message-ID: <62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>

Hi,

you can change this constant in the ndn-cxx library:

https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37 <https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37>

Not clear to me if there will be further issues because of this change though.

Hope that this helps,

Spyridon (Spyros) Mastorakis
Personal Website: http://cs.ucla.edu/~mastorakis/ <http://cs.ucla.edu/~mastorakis/>
Internet Research Laboratory
Computer Science Department
UCLA

> On Mar 28, 2017, at 11:02 AM, Mohammad Alhowaidi <malhowaidi at gmail.com> wrote:
> 
> Hello,
> 
> I was wondering how to increase NDN packet size, instead of using 8K? and is there any limitation from increasing it?
> 
> Thanks,
> Mohammad

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

From klaus at cs.arizona.EDU  Tue Mar 28 11:28:26 2017
From: klaus at cs.arizona.EDU (Klaus Schneider)
Date: Tue, 28 Mar 2017 11:28:26 -0700
Subject: [Ndn-interest] NDN packet size
In-Reply-To: <62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
References: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
	<62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
Message-ID: <e21670b1-b4a8-3db1-cb93-e3427c3c9e03@cs.arizona.edu>

In an earlier version of ndn-cxx I found that I needed to make the 
change at multiple places:

> ./ndn-cxx/src/encoding/encoding-buffer.hpp:  EncodingImpl(size_t totalReserve = 8800, size_t reserveFromBack = 400)
> ./ndn-cxx/src/encoding/encoder.hpp:  Encoder(size_t totalReserve = 8800, size_t reserveFromBack = 400);
> ./ndn-cxx/src/encoding/block.cpp:const size_t MAX_SIZE_OF_BLOCK_FROM_STREAM = 8800;
> ./ndn-cxx/src/encoding/encoder.cpp:Encoder::Encoder(size_t totalReserve/* = 8800*/, size_t reserveFromBack/* = 400*/)
> ./ndn-cxx/src/encoding/tlv.hpp:const size_t MAX_NDN_PACKET_SIZE = 8800;

Also some client libraries like jndn have the 8800 Bytes hard coded:

> ./src/net/named_data/jndn/util/Common.java:  public static final int MAX_NDN_PACKET_SIZE


Best regards,
Klaus


On 03/28/2017 11:03 AM, Spyridon (Spyros) Mastorakis wrote:
> Hi,
>
> you can change this constant in the ndn-cxx library:
>
> https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37
>
> Not clear to me if there will be further issues because of this change
> though.
>
> Hope that this helps,
>
> Spyridon (Spyros) Mastorakis
> Personal Website: http://cs.ucla.edu/~mastorakis/
> <http://cs.ucla.edu/%7Emastorakis/>
> Internet Research Laboratory
> Computer Science Department
> UCLA
>
>> On Mar 28, 2017, at 11:02 AM, Mohammad Alhowaidi <malhowaidi at gmail.com
>> <mailto:malhowaidi at gmail.com>> wrote:
>>
>> Hello,
>>
>> I was wondering how to increase NDN packet size, instead of using 8K?
>> and is there any limitation from increasing it?
>>
>> Thanks,
>> Mohammad
>
>
>
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>

From malhowaidi at gmail.com  Tue Mar 28 13:47:31 2017
From: malhowaidi at gmail.com (Mohammad Alhowaidi)
Date: Tue, 28 Mar 2017 15:47:31 -0500
Subject: [Ndn-interest] NDN packet size
In-Reply-To: <62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
References: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
	<62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
Message-ID: <CAOYiq11A5XFgy2wa5ksagp5vDb2fjSVkJpM7=0EfAZHVFLs8QA@mail.gmail.com>

I updated the file with value 32767 but it gives me the following error

ERROR: Data size exceeds maximum limit

Thanks,
Mohammad

On Tue, Mar 28, 2017 at 1:03 PM, Spyridon (Spyros) Mastorakis <
mastorakis at cs.ucla.edu> wrote:

> Hi,
>
> you can change this constant in the ndn-cxx library:
>
> https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea1c72daaffc767
> 8bf42f526b/src/encoding/tlv.hpp#L37
>
> Not clear to me if there will be further issues because of this change
> though.
>
> Hope that this helps,
>
> Spyridon (Spyros) Mastorakis
> Personal Website: http://cs.ucla.edu/~mastorakis/
> Internet Research Laboratory
> Computer Science Department
> UCLA
>
> On Mar 28, 2017, at 11:02 AM, Mohammad Alhowaidi <malhowaidi at gmail.com>
> wrote:
>
> Hello,
>
> I was wondering how to increase NDN packet size, instead of using 8K? and
> is there any limitation from increasing it?
>
> Thanks,
> Mohammad
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170328/bfbfb06b/attachment.html>

From jefft0 at remap.UCLA.EDU  Tue Mar 28 13:50:55 2017
From: jefft0 at remap.UCLA.EDU (Thompson, Jeff)
Date: Tue, 28 Mar 2017 20:50:55 +0000
Subject: [Ndn-interest] NDN packet size
In-Reply-To: <CAOYiq11A5XFgy2wa5ksagp5vDb2fjSVkJpM7=0EfAZHVFLs8QA@mail.gmail.com>
References: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
	<62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
	<CAOYiq11A5XFgy2wa5ksagp5vDb2fjSVkJpM7=0EfAZHVFLs8QA@mail.gmail.com>
Message-ID: <D5001AC9.3AE40%jefft0@remap.ucla.edu>

Which library are you using? And are you sending the packet through NFD?
- Jeff T

From: Ndn-interest <ndn-interest-bounces at lists.cs.ucla.edu<mailto:ndn-interest-bounces at lists.cs.ucla.edu>> on behalf of Mohammad Alhowaidi <malhowaidi at gmail.com<mailto:malhowaidi at gmail.com>>
Date: Tuesday, March 28, 2017 at 13:47:00
To: "Spyridon (Spyros) Mastorakis" <mastorakis at CS.UCLA.EDU<mailto:mastorakis at CS.UCLA.EDU>>
Cc: "ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>" <ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>>
Subject: Re: [Ndn-interest] NDN packet size

I updated the file with value 32767 but it gives me the following error

ERROR: Data size exceeds maximum limit

Thanks,
Mohammad

On Tue, Mar 28, 2017 at 1:03 PM, Spyridon (Spyros) Mastorakis <mastorakis at cs.ucla.edu<mailto:mastorakis at cs.ucla.edu>> wrote:
Hi,

you can change this constant in the ndn-cxx library:

https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37

Not clear to me if there will be further issues because of this change though.

Hope that this helps,

Spyridon (Spyros) Mastorakis
Personal Website: http://cs.ucla.edu/~mastorakis/
Internet Research Laboratory
Computer Science Department
UCLA

On Mar 28, 2017, at 11:02 AM, Mohammad Alhowaidi <malhowaidi at gmail.com<mailto:malhowaidi at gmail.com>> wrote:

Hello,

I was wondering how to increase NDN packet size, instead of using 8K? and is there any limitation from increasing it?

Thanks,
Mohammad


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

From malhowaidi at gmail.com  Tue Mar 28 13:53:16 2017
From: malhowaidi at gmail.com (Mohammad Alhowaidi)
Date: Tue, 28 Mar 2017 15:53:16 -0500
Subject: [Ndn-interest] NDN packet size
In-Reply-To: <d11e8e5c-717b-4b8e-8b8d-b3cf87b8485a@EMHUB6.ad.ucla.edu>
References: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
	<62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
	<CAOYiq11A5XFgy2wa5ksagp5vDb2fjSVkJpM7=0EfAZHVFLs8QA@mail.gmail.com>
	<d11e8e5c-717b-4b8e-8b8d-b3cf87b8485a@EMHUB6.ad.ucla.edu>
Message-ID: <CAOYiq11rJ_cocQgcRrG++N7OUED6va+xGA_E87C0gM-vW+jBkw@mail.gmail.com>

I am using ndn-cxx and running the ndn-tool code ( chunks). and yes I am
sending it through NFD.

Thanks,
Mohammad

On Tue, Mar 28, 2017 at 3:50 PM, Thompson, Jeff <jefft0 at remap.ucla.edu>
wrote:

> Which library are you using? And are you sending the packet through NFD?
> - Jeff T
>
> From: Ndn-interest <ndn-interest-bounces at lists.cs.ucla.edu> on behalf of
> Mohammad Alhowaidi <malhowaidi at gmail.com>
> Date: Tuesday, March 28, 2017 at 13:47:00
> To: "Spyridon (Spyros) Mastorakis" <mastorakis at CS.UCLA.EDU>
> Cc: "ndn-interest at lists.cs.ucla.edu" <ndn-interest at lists.cs.ucla.edu>
> Subject: Re: [Ndn-interest] NDN packet size
>
> I updated the file with value 32767 but it gives me the following error
>
> ERROR: Data size exceeds maximum limit
>
> Thanks,
> Mohammad
>
> On Tue, Mar 28, 2017 at 1:03 PM, Spyridon (Spyros) Mastorakis <
> mastorakis at cs.ucla.edu> wrote:
>
>> Hi,
>>
>> you can change this constant in the ndn-cxx library:
>>
>> https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea
>> 1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37
>>
>> Not clear to me if there will be further issues because of this change
>> though.
>>
>> Hope that this helps,
>>
>> Spyridon (Spyros) Mastorakis
>> Personal Website: http://cs.ucla.edu/~mastorakis/
>> Internet Research Laboratory
>> Computer Science Department
>> UCLA
>>
>> On Mar 28, 2017, at 11:02 AM, Mohammad Alhowaidi <malhowaidi at gmail.com>
>> wrote:
>>
>> Hello,
>>
>> I was wondering how to increase NDN packet size, instead of using 8K? and
>> is there any limitation from increasing it?
>>
>> Thanks,
>> Mohammad
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170328/3abdf6c0/attachment.html>

From enewberry at email.arizona.edu  Tue Mar 28 13:55:28 2017
From: enewberry at email.arizona.edu (Eric Newberry)
Date: Tue, 28 Mar 2017 13:55:28 -0700
Subject: [Ndn-interest] NDN packet size
In-Reply-To: <CAOYiq11rJ_cocQgcRrG++N7OUED6va+xGA_E87C0gM-vW+jBkw@mail.gmail.com>
References: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
	<62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
	<CAOYiq11A5XFgy2wa5ksagp5vDb2fjSVkJpM7=0EfAZHVFLs8QA@mail.gmail.com>
	<d11e8e5c-717b-4b8e-8b8d-b3cf87b8485a@EMHUB6.ad.ucla.edu>
	<CAOYiq11rJ_cocQgcRrG++N7OUED6va+xGA_E87C0gM-vW+jBkw@mail.gmail.com>
Message-ID: <CADJraSFk+Dtb-Jt8oD9Cw7EpxeeXKQv_5XcOJpgD0RrY4V31Ew@mail.gmail.com>

Did you recompile ndn-tools to use the modified ndn-cxx library?

-Eric


On Mar 28, 2017 1:53 PM, "Mohammad Alhowaidi" <malhowaidi at gmail.com> wrote:

I am using ndn-cxx and running the ndn-tool code ( chunks). and yes I am
sending it through NFD.

Thanks,
Mohammad

On Tue, Mar 28, 2017 at 3:50 PM, Thompson, Jeff <jefft0 at remap.ucla.edu>
wrote:

> Which library are you using? And are you sending the packet through NFD?
> - Jeff T
>
> From: Ndn-interest <ndn-interest-bounces at lists.cs.ucla.edu> on behalf of
> Mohammad Alhowaidi <malhowaidi at gmail.com>
> Date: Tuesday, March 28, 2017 at 13:47:00
> To: "Spyridon (Spyros) Mastorakis" <mastorakis at CS.UCLA.EDU>
> Cc: "ndn-interest at lists.cs.ucla.edu" <ndn-interest at lists.cs.ucla.edu>
> Subject: Re: [Ndn-interest] NDN packet size
>
> I updated the file with value 32767 but it gives me the following error
>
> ERROR: Data size exceeds maximum limit
>
> Thanks,
> Mohammad
>
> On Tue, Mar 28, 2017 at 1:03 PM, Spyridon (Spyros) Mastorakis <
> mastorakis at cs.ucla.edu> wrote:
>
>> Hi,
>>
>> you can change this constant in the ndn-cxx library:
>>
>> https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea
>> 1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37
>>
>> Not clear to me if there will be further issues because of this change
>> though.
>>
>> Hope that this helps,
>>
>> Spyridon (Spyros) Mastorakis
>> Personal Website: http://cs.ucla.edu/~mastorakis/
>> Internet Research Laboratory
>> Computer Science Department
>> UCLA
>>
>> On Mar 28, 2017, at 11:02 AM, Mohammad Alhowaidi <malhowaidi at gmail.com>
>> wrote:
>>
>> Hello,
>>
>> I was wondering how to increase NDN packet size, instead of using 8K? and
>> is there any limitation from increasing it?
>>
>> Thanks,
>> Mohammad
>>
>>
>>
>

_______________________________________________
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu
http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170328/d89bcf5b/attachment-0001.html>

From jefft0 at remap.UCLA.EDU  Tue Mar 28 13:55:04 2017
From: jefft0 at remap.UCLA.EDU (Thompson, Jeff)
Date: Tue, 28 Mar 2017 20:55:04 +0000
Subject: [Ndn-interest] NDN packet size
In-Reply-To: <CAOYiq11rJ_cocQgcRrG++N7OUED6va+xGA_E87C0gM-vW+jBkw@mail.gmail.com>
References: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
	<62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
	<CAOYiq11A5XFgy2wa5ksagp5vDb2fjSVkJpM7=0EfAZHVFLs8QA@mail.gmail.com>
	<d11e8e5c-717b-4b8e-8b8d-b3cf87b8485a@EMHUB6.ad.ucla.edu>
	<CAOYiq11rJ_cocQgcRrG++N7OUED6va+xGA_E87C0gM-vW+jBkw@mail.gmail.com>
Message-ID: <D5001BB3.3AE47%jefft0@remap.ucla.edu>

A question to the NFD team: To increase the packet size, is it necessary to recompile/install ndn-cxx, then recompile/install NFD?
- Jeff T

From: Mohammad Alhowaidi <malhowaidi at gmail.com<mailto:malhowaidi at gmail.com>>
Date: Tuesday, March 28, 2017 at 13:53:00
To: Jeff Thompson <jefft0 at remap.ucla.edu<mailto:jefft0 at remap.ucla.edu>>
Cc: "Spyridon (Spyros) Mastorakis" <mastorakis at cs.ucla.edu<mailto:mastorakis at cs.ucla.edu>>, "ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>" <ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>>
Subject: Re: [Ndn-interest] NDN packet size

I am using ndn-cxx and running the ndn-tool code ( chunks). and yes I am sending it through NFD.

Thanks,
Mohammad

On Tue, Mar 28, 2017 at 3:50 PM, Thompson, Jeff <jefft0 at remap.ucla.edu<mailto:jefft0 at remap.ucla.edu>> wrote:
Which library are you using? And are you sending the packet through NFD?
- Jeff T

From: Ndn-interest <ndn-interest-bounces at lists.cs.ucla.edu<mailto:ndn-interest-bounces at lists.cs.ucla.edu>> on behalf of Mohammad Alhowaidi <malhowaidi at gmail.com<mailto:malhowaidi at gmail.com>>
Date: Tuesday, March 28, 2017 at 13:47:00
To: "Spyridon (Spyros) Mastorakis" <mastorakis at CS.UCLA.EDU<mailto:mastorakis at CS.UCLA.EDU>>
Cc: "ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>" <ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>>
Subject: Re: [Ndn-interest] NDN packet size

I updated the file with value 32767 but it gives me the following error

ERROR: Data size exceeds maximum limit

Thanks,
Mohammad

On Tue, Mar 28, 2017 at 1:03 PM, Spyridon (Spyros) Mastorakis <mastorakis at cs.ucla.edu<mailto:mastorakis at cs.ucla.edu>> wrote:
Hi,

you can change this constant in the ndn-cxx library:

https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37

Not clear to me if there will be further issues because of this change though.

Hope that this helps,

Spyridon (Spyros) Mastorakis
Personal Website: http://cs.ucla.edu/~mastorakis/
Internet Research Laboratory
Computer Science Department
UCLA

On Mar 28, 2017, at 11:02 AM, Mohammad Alhowaidi <malhowaidi at gmail.com<mailto:malhowaidi at gmail.com>> wrote:

Hello,

I was wondering how to increase NDN packet size, instead of using 8K? and is there any limitation from increasing it?

Thanks,
Mohammad



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

From malhowaidi at gmail.com  Tue Mar 28 14:00:50 2017
From: malhowaidi at gmail.com (Mohammad Alhowaidi)
Date: Tue, 28 Mar 2017 16:00:50 -0500
Subject: [Ndn-interest] NDN packet size
In-Reply-To: <CADJraSFk+Dtb-Jt8oD9Cw7EpxeeXKQv_5XcOJpgD0RrY4V31Ew@mail.gmail.com>
References: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
	<62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
	<CAOYiq11A5XFgy2wa5ksagp5vDb2fjSVkJpM7=0EfAZHVFLs8QA@mail.gmail.com>
	<d11e8e5c-717b-4b8e-8b8d-b3cf87b8485a@EMHUB6.ad.ucla.edu>
	<CAOYiq11rJ_cocQgcRrG++N7OUED6va+xGA_E87C0gM-vW+jBkw@mail.gmail.com>
	<CADJraSFk+Dtb-Jt8oD9Cw7EpxeeXKQv_5XcOJpgD0RrY4V31Ew@mail.gmail.com>
Message-ID: <CAOYiq12Qq5uj0=jgvqaxyJDPTRosGfzBvDpXi=mJuigLE29KGQ@mail.gmail.com>

Yes , I recompiled ndn-cxx, NFD , and ndn-tools.

Thanks,
Mohammad

On Tue, Mar 28, 2017 at 3:55 PM, Eric Newberry <enewberry at email.arizona.edu>
wrote:

> Did you recompile ndn-tools to use the modified ndn-cxx library?
>
> -Eric
>
>
> On Mar 28, 2017 1:53 PM, "Mohammad Alhowaidi" <malhowaidi at gmail.com>
> wrote:
>
> I am using ndn-cxx and running the ndn-tool code ( chunks). and yes I am
> sending it through NFD.
>
> Thanks,
> Mohammad
>
> On Tue, Mar 28, 2017 at 3:50 PM, Thompson, Jeff <jefft0 at remap.ucla.edu>
> wrote:
>
>> Which library are you using? And are you sending the packet through NFD?
>> - Jeff T
>>
>> From: Ndn-interest <ndn-interest-bounces at lists.cs.ucla.edu> on behalf of
>> Mohammad Alhowaidi <malhowaidi at gmail.com>
>> Date: Tuesday, March 28, 2017 at 13:47:00
>> To: "Spyridon (Spyros) Mastorakis" <mastorakis at CS.UCLA.EDU>
>> Cc: "ndn-interest at lists.cs.ucla.edu" <ndn-interest at lists.cs.ucla.edu>
>> Subject: Re: [Ndn-interest] NDN packet size
>>
>> I updated the file with value 32767 but it gives me the following error
>>
>> ERROR: Data size exceeds maximum limit
>>
>> Thanks,
>> Mohammad
>>
>> On Tue, Mar 28, 2017 at 1:03 PM, Spyridon (Spyros) Mastorakis <
>> mastorakis at cs.ucla.edu> wrote:
>>
>>> Hi,
>>>
>>> you can change this constant in the ndn-cxx library:
>>>
>>> https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea
>>> 1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37
>>>
>>> Not clear to me if there will be further issues because of this change
>>> though.
>>>
>>> Hope that this helps,
>>>
>>> Spyridon (Spyros) Mastorakis
>>> Personal Website: http://cs.ucla.edu/~mastorakis/
>>> Internet Research Laboratory
>>> Computer Science Department
>>> UCLA
>>>
>>> On Mar 28, 2017, at 11:02 AM, Mohammad Alhowaidi <malhowaidi at gmail.com>
>>> wrote:
>>>
>>> Hello,
>>>
>>> I was wondering how to increase NDN packet size, instead of using 8K?
>>> and is there any limitation from increasing it?
>>>
>>> Thanks,
>>> Mohammad
>>>
>>>
>>>
>>
>
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170328/45150bf7/attachment.html>

From aa at CS.UCLA.EDU  Tue Mar 28 14:01:39 2017
From: aa at CS.UCLA.EDU (Alex Afanasyev)
Date: Tue, 28 Mar 2017 16:01:39 -0500
Subject: [Ndn-interest] NDN packet size
In-Reply-To: <D5001BB3.3AE47%jefft0@remap.ucla.edu>
References: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
	<62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
	<CAOYiq11A5XFgy2wa5ksagp5vDb2fjSVkJpM7=0EfAZHVFLs8QA@mail.gmail.com>
	<d11e8e5c-717b-4b8e-8b8d-b3cf87b8485a@EMHUB6.ad.ucla.edu>
	<CAOYiq11rJ_cocQgcRrG++N7OUED6va+xGA_E87C0gM-vW+jBkw@mail.gmail.com>
	<D5001BB3.3AE47%jefft0@remap.ucla.edu>
Message-ID: <27D01C90-0661-4189-A2AF-E6526A9E7F59@cs.ucla.edu>

The new ndn-cxx needs to be recompiled and installed, after which all other tools and code needs to be recompiled and reinstalled.

The packet size is used as a compile-time constant in several places (definitely in NFD, not sure about tools), which requires such recompilation.

--
Alex

> On Mar 28, 2017, at 3:55 PM, Thompson, Jeff <jefft0 at remap.UCLA.EDU> wrote:
> 
> A question to the NFD team: To increase the packet size, is it necessary to recompile/install ndn-cxx, then recompile/install NFD?
> - Jeff T
> 
> From: Mohammad Alhowaidi <malhowaidi at gmail.com <mailto:malhowaidi at gmail.com>>
> Date: Tuesday, March 28, 2017 at 13:53:00
> To: Jeff Thompson <jefft0 at remap.ucla.edu <mailto:jefft0 at remap.ucla.edu>>
> Cc: "Spyridon (Spyros) Mastorakis" <mastorakis at cs.ucla.edu <mailto:mastorakis at cs.ucla.edu>>, "ndn-interest at lists.cs.ucla.edu <mailto:ndn-interest at lists.cs.ucla.edu>" <ndn-interest at lists.cs.ucla.edu <mailto:ndn-interest at lists.cs.ucla.edu>>
> Subject: Re: [Ndn-interest] NDN packet size
> 
> I am using ndn-cxx and running the ndn-tool code ( chunks). and yes I am sending it through NFD.
> 
> Thanks,
> Mohammad
> 
> On Tue, Mar 28, 2017 at 3:50 PM, Thompson, Jeff <jefft0 at remap.ucla.edu <mailto:jefft0 at remap.ucla.edu>> wrote:
>> Which library are you using? And are you sending the packet through NFD?
>> - Jeff T
>> 
>> From: Ndn-interest <ndn-interest-bounces at lists.cs.ucla.edu <mailto:ndn-interest-bounces at lists.cs.ucla.edu>> on behalf of Mohammad Alhowaidi <malhowaidi at gmail.com <mailto:malhowaidi at gmail.com>>
>> Date: Tuesday, March 28, 2017 at 13:47:00
>> To: "Spyridon (Spyros) Mastorakis" <mastorakis at CS.UCLA.EDU <mailto:mastorakis at CS.UCLA.EDU>>
>> Cc: "ndn-interest at lists.cs.ucla.edu <mailto:ndn-interest at lists.cs.ucla.edu>" <ndn-interest at lists.cs.ucla.edu <mailto:ndn-interest at lists.cs.ucla.edu>>
>> Subject: Re: [Ndn-interest] NDN packet size
>> 
>> I updated the file with value 32767 but it gives me the following error 
>> 
>> ERROR: Data size exceeds maximum limit
>> 
>> Thanks,
>> Mohammad
>> 
>> On Tue, Mar 28, 2017 at 1:03 PM, Spyridon (Spyros) Mastorakis <mastorakis at cs.ucla.edu <mailto:mastorakis at cs.ucla.edu>> wrote:
>>> Hi,
>>> 
>>> you can change this constant in the ndn-cxx library:
>>> 
>>> https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37 <https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37>
>>> 
>>> Not clear to me if there will be further issues because of this change though.
>>> 
>>> Hope that this helps,
>>> 
>>> Spyridon (Spyros) Mastorakis
>>> Personal Website: http://cs.ucla.edu/~mastorakis/ <http://cs.ucla.edu/~mastorakis/>
>>> Internet Research Laboratory
>>> Computer Science Department
>>> UCLA
>>> 
>>>> On Mar 28, 2017, at 11:02 AM, Mohammad Alhowaidi <malhowaidi at gmail.com <mailto:malhowaidi at gmail.com>> wrote:
>>>> 
>>>> Hello,
>>>> 
>>>> I was wondering how to increase NDN packet size, instead of using 8K? and is there any limitation from increasing it?
>>>> 
>>>> Thanks,
>>>> Mohammad
>>> 
>> 
> 
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest

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

From klaus at cs.arizona.EDU  Tue Mar 28 14:35:32 2017
From: klaus at cs.arizona.EDU (Klaus Schneider)
Date: Tue, 28 Mar 2017 14:35:32 -0700
Subject: [Ndn-interest] NDN packet size
In-Reply-To: <27D01C90-0661-4189-A2AF-E6526A9E7F59@cs.ucla.edu>
References: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
	<62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
	<CAOYiq11A5XFgy2wa5ksagp5vDb2fjSVkJpM7=0EfAZHVFLs8QA@mail.gmail.com>
	<d11e8e5c-717b-4b8e-8b8d-b3cf87b8485a@EMHUB6.ad.ucla.edu>
	<CAOYiq11rJ_cocQgcRrG++N7OUED6va+xGA_E87C0gM-vW+jBkw@mail.gmail.com>
	<D5001BB3.3AE47%jefft0@remap.ucla.edu>
	<27D01C90-0661-4189-A2AF-E6526A9E7F59@cs.ucla.edu>
Message-ID: <c47ef76d-2e4d-8adf-7547-46c81197158c@cs.arizona.edu>

Btw, what was the reason for setting the default max packet size to 8800 
in the first place?

Is there any drawback to increasing the default, to let's say 1 Megabyte?

Best regards,
Klaus



On 03/28/2017 02:01 PM, Alex Afanasyev wrote:
> The new ndn-cxx needs to be recompiled and installed, after which all
> other tools and code needs to be recompiled and reinstalled.
>
> The packet size is used as a compile-time constant in several places
> (definitely in NFD, not sure about tools), which requires such
> recompilation.
>
> --
> Alex
>
>> On Mar 28, 2017, at 3:55 PM, Thompson, Jeff <jefft0 at remap.UCLA.EDU
>> <mailto:jefft0 at remap.UCLA.EDU>> wrote:
>>
>> A question to the NFD team: To increase the packet size, is it
>> necessary to recompile/install ndn-cxx, then recompile/install NFD?
>> - Jeff T
>>
>> From: Mohammad Alhowaidi <malhowaidi at gmail.com
>> <mailto:malhowaidi at gmail.com>>
>> Date: Tuesday, March 28, 2017 at 13:53:00
>> To: Jeff Thompson <jefft0 at remap.ucla.edu <mailto:jefft0 at remap.ucla.edu>>
>> Cc: "Spyridon (Spyros) Mastorakis" <mastorakis at cs.ucla.edu
>> <mailto:mastorakis at cs.ucla.edu>>, "ndn-interest at lists.cs.ucla.edu
>> <mailto:ndn-interest at lists.cs.ucla.edu>"
>> <ndn-interest at lists.cs.ucla.edu <mailto:ndn-interest at lists.cs.ucla.edu>>
>> Subject: Re: [Ndn-interest] NDN packet size
>>
>> I am using ndn-cxx and running the ndn-tool code ( chunks). and yes I
>> am sending it through NFD.
>>
>> Thanks,
>> Mohammad
>>
>> On Tue, Mar 28, 2017 at 3:50 PM, Thompson, Jeff <jefft0 at remap.ucla.edu
>> <mailto:jefft0 at remap.ucla.edu>> wrote:
>>> Which library are you using? And are you sending the packet through NFD?
>>> - Jeff T
>>>
>>> From: Ndn-interest <ndn-interest-bounces at lists.cs.ucla.edu
>>> <mailto:ndn-interest-bounces at lists.cs.ucla.edu>> on behalf of
>>> Mohammad Alhowaidi <malhowaidi at gmail.com <mailto:malhowaidi at gmail.com>>
>>> Date: Tuesday, March 28, 2017 at 13:47:00
>>> To: "Spyridon (Spyros) Mastorakis" <mastorakis at CS.UCLA.EDU
>>> <mailto:mastorakis at CS.UCLA.EDU>>
>>> Cc: "ndn-interest at lists.cs.ucla.edu
>>> <mailto:ndn-interest at lists.cs.ucla.edu>"
>>> <ndn-interest at lists.cs.ucla.edu <mailto:ndn-interest at lists.cs.ucla.edu>>
>>> Subject: Re: [Ndn-interest] NDN packet size
>>>
>>> I updated the file with value 32767 but it gives me the following error
>>>
>>> ERROR: Data size exceeds maximum limit
>>>
>>> Thanks,
>>> Mohammad
>>>
>>> On Tue, Mar 28, 2017 at 1:03 PM, Spyridon (Spyros) Mastorakis
>>> <mastorakis at cs.ucla.edu <mailto:mastorakis at cs.ucla.edu>> wrote:
>>>> Hi,
>>>>
>>>> you can change this constant in the ndn-cxx library:
>>>>
>>>> https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37
>>>> <https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37>
>>>>
>>>> Not clear to me if there will be further issues because of this
>>>> change though.
>>>>
>>>> Hope that this helps,
>>>>
>>>> Spyridon (Spyros) Mastorakis
>>>> Personal Website: http://cs.ucla.edu/~mastorakis/
>>>> <http://cs.ucla.edu/%7Emastorakis/>
>>>> Internet Research Laboratory
>>>> Computer Science Department
>>>> UCLA
>>>>
>>>>> On Mar 28, 2017, at 11:02 AM, Mohammad Alhowaidi
>>>>> <malhowaidi at gmail.com <mailto:malhowaidi at gmail.com>> wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> I was wondering how to increase NDN packet size, instead of using
>>>>> 8K? and is there any limitation from increasing it?
>>>>>
>>>>> Thanks,
>>>>> Mohammad
>>>>
>>>
>>
>> _______________________________________________
>> Ndn-interest mailing list
>> Ndn-interest at lists.cs.ucla.edu <mailto:Ndn-interest at lists.cs.ucla.edu>
>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>
>
>
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>

From nicholas.h.briggs at gmail.com  Tue Mar 28 14:40:22 2017
From: nicholas.h.briggs at gmail.com (Nick Briggs)
Date: Tue, 28 Mar 2017 14:40:22 -0700
Subject: [Ndn-interest] NDN packet size
In-Reply-To: <c47ef76d-2e4d-8adf-7547-46c81197158c@cs.arizona.edu>
References: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
	<62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
	<CAOYiq11A5XFgy2wa5ksagp5vDb2fjSVkJpM7=0EfAZHVFLs8QA@mail.gmail.com>
	<d11e8e5c-717b-4b8e-8b8d-b3cf87b8485a@EMHUB6.ad.ucla.edu>
	<CAOYiq11rJ_cocQgcRrG++N7OUED6va+xGA_E87C0gM-vW+jBkw@mail.gmail.com>
	<D5001BB3.3AE47%jefft0@remap.ucla.edu>
	<27D01C90-0661-4189-A2AF-E6526A9E7F59@cs.ucla.edu>
	<c47ef76d-2e4d-8adf-7547-46c81197158c@cs.arizona.edu>
Message-ID: <4F059F41-3644-41EE-BD64-6AF95988A491@gmail.com>

It gets you 8K bytes of data along with necessary metadata and a name that isn't too long in a Content packet.
It can be encapsulated in a UDP packet with about 6 fragments when you're do IP encapsulation. (max UDP is 64K bytes)
It fits within a 9000 byte jumbo ethernet frame if you're doing direct ethernet encapsulation.

-- Nick Briggs

> On Mar 28, 2017, at 2:35 PM, Klaus Schneider <klaus at cs.arizona.EDU> wrote:
> 
> Btw, what was the reason for setting the default max packet size to 8800 in the first place?
> 
> Is there any drawback to increasing the default, to let's say 1 Megabyte?
> 
> Best regards,
> Klaus
> 
> 
> 
> On 03/28/2017 02:01 PM, Alex Afanasyev wrote:
>> The new ndn-cxx needs to be recompiled and installed, after which all
>> other tools and code needs to be recompiled and reinstalled.
>> 
>> The packet size is used as a compile-time constant in several places
>> (definitely in NFD, not sure about tools), which requires such
>> recompilation.
>> 
>> --
>> Alex
>> 
>>> On Mar 28, 2017, at 3:55 PM, Thompson, Jeff <jefft0 at remap.UCLA.EDU
>>> <mailto:jefft0 at remap.UCLA.EDU>> wrote:
>>> 
>>> A question to the NFD team: To increase the packet size, is it
>>> necessary to recompile/install ndn-cxx, then recompile/install NFD?
>>> - Jeff T
>>> 
>>> From: Mohammad Alhowaidi <malhowaidi at gmail.com
>>> <mailto:malhowaidi at gmail.com>>
>>> Date: Tuesday, March 28, 2017 at 13:53:00
>>> To: Jeff Thompson <jefft0 at remap.ucla.edu <mailto:jefft0 at remap.ucla.edu>>
>>> Cc: "Spyridon (Spyros) Mastorakis" <mastorakis at cs.ucla.edu
>>> <mailto:mastorakis at cs.ucla.edu>>, "ndn-interest at lists.cs.ucla.edu
>>> <mailto:ndn-interest at lists.cs.ucla.edu>"
>>> <ndn-interest at lists.cs.ucla.edu <mailto:ndn-interest at lists.cs.ucla.edu>>
>>> Subject: Re: [Ndn-interest] NDN packet size
>>> 
>>> I am using ndn-cxx and running the ndn-tool code ( chunks). and yes I
>>> am sending it through NFD.
>>> 
>>> Thanks,
>>> Mohammad
>>> 
>>> On Tue, Mar 28, 2017 at 3:50 PM, Thompson, Jeff <jefft0 at remap.ucla.edu
>>> <mailto:jefft0 at remap.ucla.edu>> wrote:
>>>> Which library are you using? And are you sending the packet through NFD?
>>>> - Jeff T
>>>> 
>>>> From: Ndn-interest <ndn-interest-bounces at lists.cs.ucla.edu
>>>> <mailto:ndn-interest-bounces at lists.cs.ucla.edu>> on behalf of
>>>> Mohammad Alhowaidi <malhowaidi at gmail.com <mailto:malhowaidi at gmail.com>>
>>>> Date: Tuesday, March 28, 2017 at 13:47:00
>>>> To: "Spyridon (Spyros) Mastorakis" <mastorakis at CS.UCLA.EDU
>>>> <mailto:mastorakis at CS.UCLA.EDU>>
>>>> Cc: "ndn-interest at lists.cs.ucla.edu
>>>> <mailto:ndn-interest at lists.cs.ucla.edu>"
>>>> <ndn-interest at lists.cs.ucla.edu <mailto:ndn-interest at lists.cs.ucla.edu>>
>>>> Subject: Re: [Ndn-interest] NDN packet size
>>>> 
>>>> I updated the file with value 32767 but it gives me the following error
>>>> 
>>>> ERROR: Data size exceeds maximum limit
>>>> 
>>>> Thanks,
>>>> Mohammad
>>>> 
>>>> On Tue, Mar 28, 2017 at 1:03 PM, Spyridon (Spyros) Mastorakis
>>>> <mastorakis at cs.ucla.edu <mailto:mastorakis at cs.ucla.edu>> wrote:
>>>>> Hi,
>>>>> 
>>>>> you can change this constant in the ndn-cxx library:
>>>>> 
>>>>> https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37
>>>>> <https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37>
>>>>> 
>>>>> Not clear to me if there will be further issues because of this
>>>>> change though.
>>>>> 
>>>>> Hope that this helps,
>>>>> 
>>>>> Spyridon (Spyros) Mastorakis
>>>>> Personal Website: http://cs.ucla.edu/~mastorakis/
>>>>> <http://cs.ucla.edu/%7Emastorakis/>
>>>>> Internet Research Laboratory
>>>>> Computer Science Department
>>>>> UCLA
>>>>> 
>>>>>> On Mar 28, 2017, at 11:02 AM, Mohammad Alhowaidi
>>>>>> <malhowaidi at gmail.com <mailto:malhowaidi at gmail.com>> wrote:
>>>>>> 
>>>>>> Hello,
>>>>>> 
>>>>>> I was wondering how to increase NDN packet size, instead of using
>>>>>> 8K? and is there any limitation from increasing it?
>>>>>> 
>>>>>> Thanks,
>>>>>> Mohammad
>>>>> 
>>>> 
>>> 
>>> _______________________________________________
>>> Ndn-interest mailing list
>>> Ndn-interest at lists.cs.ucla.edu <mailto:Ndn-interest at lists.cs.ucla.edu>
>>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>> 
>> 
>> 
>> _______________________________________________
>> 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 klaus at cs.arizona.EDU  Tue Mar 28 14:45:48 2017
From: klaus at cs.arizona.EDU (Klaus Schneider)
Date: Tue, 28 Mar 2017 14:45:48 -0700
Subject: [Ndn-interest] NDN packet size
In-Reply-To: <4F059F41-3644-41EE-BD64-6AF95988A491@gmail.com>
References: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
	<62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
	<CAOYiq11A5XFgy2wa5ksagp5vDb2fjSVkJpM7=0EfAZHVFLs8QA@mail.gmail.com>
	<d11e8e5c-717b-4b8e-8b8d-b3cf87b8485a@EMHUB6.ad.ucla.edu>
	<CAOYiq11rJ_cocQgcRrG++N7OUED6va+xGA_E87C0gM-vW+jBkw@mail.gmail.com>
	<D5001BB3.3AE47%jefft0@remap.ucla.edu>
	<27D01C90-0661-4189-A2AF-E6526A9E7F59@cs.ucla.edu>
	<c47ef76d-2e4d-8adf-7547-46c81197158c@cs.arizona.edu>
	<4F059F41-3644-41EE-BD64-6AF95988A491@gmail.com>
Message-ID: <eb256f8b-b28b-7c94-d83b-94727cdaffa3@cs.arizona.edu>

Those are all good reasons. Thanks for the clarification.

Klaus

On 03/28/2017 02:40 PM, Nick Briggs wrote:
> It gets you 8K bytes of data along with necessary metadata and a name that isn't too long in a Content packet.
> It can be encapsulated in a UDP packet with about 6 fragments when you're do IP encapsulation. (max UDP is 64K bytes)
> It fits within a 9000 byte jumbo ethernet frame if you're doing direct ethernet encapsulation.
>
> -- Nick Briggs
>
>> On Mar 28, 2017, at 2:35 PM, Klaus Schneider <klaus at cs.arizona.EDU> wrote:
>>
>> Btw, what was the reason for setting the default max packet size to 8800 in the first place?
>>
>> Is there any drawback to increasing the default, to let's say 1 Megabyte?
>>
>> Best regards,
>> Klaus
>>
>>
>>
>> On 03/28/2017 02:01 PM, Alex Afanasyev wrote:
>>> The new ndn-cxx needs to be recompiled and installed, after which all
>>> other tools and code needs to be recompiled and reinstalled.
>>>
>>> The packet size is used as a compile-time constant in several places
>>> (definitely in NFD, not sure about tools), which requires such
>>> recompilation.
>>>
>>> --
>>> Alex
>>>
>>>> On Mar 28, 2017, at 3:55 PM, Thompson, Jeff <jefft0 at remap.UCLA.EDU
>>>> <mailto:jefft0 at remap.UCLA.EDU>> wrote:
>>>>
>>>> A question to the NFD team: To increase the packet size, is it
>>>> necessary to recompile/install ndn-cxx, then recompile/install NFD?
>>>> - Jeff T
>>>>
>>>> From: Mohammad Alhowaidi <malhowaidi at gmail.com
>>>> <mailto:malhowaidi at gmail.com>>
>>>> Date: Tuesday, March 28, 2017 at 13:53:00
>>>> To: Jeff Thompson <jefft0 at remap.ucla.edu <mailto:jefft0 at remap.ucla.edu>>
>>>> Cc: "Spyridon (Spyros) Mastorakis" <mastorakis at cs.ucla.edu
>>>> <mailto:mastorakis at cs.ucla.edu>>, "ndn-interest at lists.cs.ucla.edu
>>>> <mailto:ndn-interest at lists.cs.ucla.edu>"
>>>> <ndn-interest at lists.cs.ucla.edu <mailto:ndn-interest at lists.cs.ucla.edu>>
>>>> Subject: Re: [Ndn-interest] NDN packet size
>>>>
>>>> I am using ndn-cxx and running the ndn-tool code ( chunks). and yes I
>>>> am sending it through NFD.
>>>>
>>>> Thanks,
>>>> Mohammad
>>>>
>>>> On Tue, Mar 28, 2017 at 3:50 PM, Thompson, Jeff <jefft0 at remap.ucla.edu
>>>> <mailto:jefft0 at remap.ucla.edu>> wrote:
>>>>> Which library are you using? And are you sending the packet through NFD?
>>>>> - Jeff T
>>>>>
>>>>> From: Ndn-interest <ndn-interest-bounces at lists.cs.ucla.edu
>>>>> <mailto:ndn-interest-bounces at lists.cs.ucla.edu>> on behalf of
>>>>> Mohammad Alhowaidi <malhowaidi at gmail.com <mailto:malhowaidi at gmail.com>>
>>>>> Date: Tuesday, March 28, 2017 at 13:47:00
>>>>> To: "Spyridon (Spyros) Mastorakis" <mastorakis at CS.UCLA.EDU
>>>>> <mailto:mastorakis at CS.UCLA.EDU>>
>>>>> Cc: "ndn-interest at lists.cs.ucla.edu
>>>>> <mailto:ndn-interest at lists.cs.ucla.edu>"
>>>>> <ndn-interest at lists.cs.ucla.edu <mailto:ndn-interest at lists.cs.ucla.edu>>
>>>>> Subject: Re: [Ndn-interest] NDN packet size
>>>>>
>>>>> I updated the file with value 32767 but it gives me the following error
>>>>>
>>>>> ERROR: Data size exceeds maximum limit
>>>>>
>>>>> Thanks,
>>>>> Mohammad
>>>>>
>>>>> On Tue, Mar 28, 2017 at 1:03 PM, Spyridon (Spyros) Mastorakis
>>>>> <mastorakis at cs.ucla.edu <mailto:mastorakis at cs.ucla.edu>> wrote:
>>>>>> Hi,
>>>>>>
>>>>>> you can change this constant in the ndn-cxx library:
>>>>>>
>>>>>> https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37
>>>>>> <https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37>
>>>>>>
>>>>>> Not clear to me if there will be further issues because of this
>>>>>> change though.
>>>>>>
>>>>>> Hope that this helps,
>>>>>>
>>>>>> Spyridon (Spyros) Mastorakis
>>>>>> Personal Website: http://cs.ucla.edu/~mastorakis/
>>>>>> <http://cs.ucla.edu/%7Emastorakis/>
>>>>>> Internet Research Laboratory
>>>>>> Computer Science Department
>>>>>> UCLA
>>>>>>
>>>>>>> On Mar 28, 2017, at 11:02 AM, Mohammad Alhowaidi
>>>>>>> <malhowaidi at gmail.com <mailto:malhowaidi at gmail.com>> wrote:
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> I was wondering how to increase NDN packet size, instead of using
>>>>>>> 8K? and is there any limitation from increasing it?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Mohammad
>>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Ndn-interest mailing list
>>>> Ndn-interest at lists.cs.ucla.edu <mailto:Ndn-interest at lists.cs.ucla.edu>
>>>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>>>
>>>
>>>
>>> _______________________________________________
>>> 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 nicholas.h.briggs at gmail.com  Tue Mar 28 14:54:30 2017
From: nicholas.h.briggs at gmail.com (Nick Briggs)
Date: Tue, 28 Mar 2017 14:54:30 -0700
Subject: [Ndn-interest] NDN packet size
In-Reply-To: <eb256f8b-b28b-7c94-d83b-94727cdaffa3@cs.arizona.edu>
References: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
	<62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
	<CAOYiq11A5XFgy2wa5ksagp5vDb2fjSVkJpM7=0EfAZHVFLs8QA@mail.gmail.com>
	<d11e8e5c-717b-4b8e-8b8d-b3cf87b8485a@EMHUB6.ad.ucla.edu>
	<CAOYiq11rJ_cocQgcRrG++N7OUED6va+xGA_E87C0gM-vW+jBkw@mail.gmail.com>
	<D5001BB3.3AE47%jefft0@remap.ucla.edu>
	<27D01C90-0661-4189-A2AF-E6526A9E7F59@cs.ucla.edu>
	<c47ef76d-2e4d-8adf-7547-46c81197158c@cs.arizona.edu>
	<4F059F41-3644-41EE-BD64-6AF95988A491@gmail.com>
	<eb256f8b-b28b-7c94-d83b-94727cdaffa3@cs.arizona.edu>
Message-ID: <DF41EF63-AE59-4D02-96EB-51EEC1C75F21@gmail.com>

And one other that we found to be a bit of a headache --

$ uname -a
FreeBSD pigeon 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0: Wed Feb 22 06:06:13 UTC 2017     root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  i386
$ sysctl net.inet.udp.maxdgram
net.inet.udp.maxdgram: 9216

$ uname -a
Darwin silversword 15.6.0 Darwin Kernel Version 15.6.0: Fri Feb 17 10:21:18 PST 2017; root:xnu-3248.60.11.4.1~1/RELEASE_X86_64 x86_64
$ sysctl net.inet.udp.maxdgram
net.inet.udp.maxdgram: 9216

I don't happen to have a Linux box handy to check there.

> On Mar 28, 2017, at 2:45 PM, Klaus Schneider <klaus at cs.arizona.edu> wrote:
> 
> Those are all good reasons. Thanks for the clarification.
> 
> Klaus
> 
> On 03/28/2017 02:40 PM, Nick Briggs wrote:
>> It gets you 8K bytes of data along with necessary metadata and a name that isn't too long in a Content packet.
>> It can be encapsulated in a UDP packet with about 6 fragments when you're do IP encapsulation. (max UDP is 64K bytes)
>> It fits within a 9000 byte jumbo ethernet frame if you're doing direct ethernet encapsulation.
>> 
>> -- Nick Briggs
>> 
>>> On Mar 28, 2017, at 2:35 PM, Klaus Schneider <klaus at cs.arizona.EDU> wrote:
>>> 
>>> Btw, what was the reason for setting the default max packet size to 8800 in the first place?
>>> 
>>> Is there any drawback to increasing the default, to let's say 1 Megabyte?
>>> 
>>> Best regards,
>>> Klaus
>>> 
>>> 
>>> 
>>> On 03/28/2017 02:01 PM, Alex Afanasyev wrote:
>>>> The new ndn-cxx needs to be recompiled and installed, after which all
>>>> other tools and code needs to be recompiled and reinstalled.
>>>> 
>>>> The packet size is used as a compile-time constant in several places
>>>> (definitely in NFD, not sure about tools), which requires such
>>>> recompilation.
>>>> 
>>>> --
>>>> Alex
>>>> 
>>>>> On Mar 28, 2017, at 3:55 PM, Thompson, Jeff <jefft0 at remap.UCLA.EDU
>>>>> <mailto:jefft0 at remap.UCLA.EDU>> wrote:
>>>>> 
>>>>> A question to the NFD team: To increase the packet size, is it
>>>>> necessary to recompile/install ndn-cxx, then recompile/install NFD?
>>>>> - Jeff T
>>>>> 
>>>>> From: Mohammad Alhowaidi <malhowaidi at gmail.com
>>>>> <mailto:malhowaidi at gmail.com>>
>>>>> Date: Tuesday, March 28, 2017 at 13:53:00
>>>>> To: Jeff Thompson <jefft0 at remap.ucla.edu <mailto:jefft0 at remap.ucla.edu>>
>>>>> Cc: "Spyridon (Spyros) Mastorakis" <mastorakis at cs.ucla.edu
>>>>> <mailto:mastorakis at cs.ucla.edu>>, "ndn-interest at lists.cs.ucla.edu
>>>>> <mailto:ndn-interest at lists.cs.ucla.edu>"
>>>>> <ndn-interest at lists.cs.ucla.edu <mailto:ndn-interest at lists.cs.ucla.edu>>
>>>>> Subject: Re: [Ndn-interest] NDN packet size
>>>>> 
>>>>> I am using ndn-cxx and running the ndn-tool code ( chunks). and yes I
>>>>> am sending it through NFD.
>>>>> 
>>>>> Thanks,
>>>>> Mohammad
>>>>> 
>>>>> On Tue, Mar 28, 2017 at 3:50 PM, Thompson, Jeff <jefft0 at remap.ucla.edu
>>>>> <mailto:jefft0 at remap.ucla.edu>> wrote:
>>>>>> Which library are you using? And are you sending the packet through NFD?
>>>>>> - Jeff T
>>>>>> 
>>>>>> From: Ndn-interest <ndn-interest-bounces at lists.cs.ucla.edu
>>>>>> <mailto:ndn-interest-bounces at lists.cs.ucla.edu>> on behalf of
>>>>>> Mohammad Alhowaidi <malhowaidi at gmail.com <mailto:malhowaidi at gmail.com>>
>>>>>> Date: Tuesday, March 28, 2017 at 13:47:00
>>>>>> To: "Spyridon (Spyros) Mastorakis" <mastorakis at CS.UCLA.EDU
>>>>>> <mailto:mastorakis at CS.UCLA.EDU>>
>>>>>> Cc: "ndn-interest at lists.cs.ucla.edu
>>>>>> <mailto:ndn-interest at lists.cs.ucla.edu>"
>>>>>> <ndn-interest at lists.cs.ucla.edu <mailto:ndn-interest at lists.cs.ucla.edu>>
>>>>>> Subject: Re: [Ndn-interest] NDN packet size
>>>>>> 
>>>>>> I updated the file with value 32767 but it gives me the following error
>>>>>> 
>>>>>> ERROR: Data size exceeds maximum limit
>>>>>> 
>>>>>> Thanks,
>>>>>> Mohammad
>>>>>> 
>>>>>> On Tue, Mar 28, 2017 at 1:03 PM, Spyridon (Spyros) Mastorakis
>>>>>> <mastorakis at cs.ucla.edu <mailto:mastorakis at cs.ucla.edu>> wrote:
>>>>>>> Hi,
>>>>>>> 
>>>>>>> you can change this constant in the ndn-cxx library:
>>>>>>> 
>>>>>>> https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37
>>>>>>> <https://github.com/named-data/ndn-cxx/blob/e78eeca5cc6c882ea1c72daaffc7678bf42f526b/src/encoding/tlv.hpp#L37>
>>>>>>> 
>>>>>>> Not clear to me if there will be further issues because of this
>>>>>>> change though.
>>>>>>> 
>>>>>>> Hope that this helps,
>>>>>>> 
>>>>>>> Spyridon (Spyros) Mastorakis
>>>>>>> Personal Website: http://cs.ucla.edu/~mastorakis/
>>>>>>> <http://cs.ucla.edu/%7Emastorakis/>
>>>>>>> Internet Research Laboratory
>>>>>>> Computer Science Department
>>>>>>> UCLA
>>>>>>> 
>>>>>>>> On Mar 28, 2017, at 11:02 AM, Mohammad Alhowaidi
>>>>>>>> <malhowaidi at gmail.com <mailto:malhowaidi at gmail.com>> wrote:
>>>>>>>> 
>>>>>>>> Hello,
>>>>>>>> 
>>>>>>>> I was wondering how to increase NDN packet size, instead of using
>>>>>>>> 8K? and is there any limitation from increasing it?
>>>>>>>> 
>>>>>>>> Thanks,
>>>>>>>> Mohammad
>>>>>>> 
>>>>>> 
>>>>> 
>>>>> _______________________________________________
>>>>> Ndn-interest mailing list
>>>>> Ndn-interest at lists.cs.ucla.edu <mailto:Ndn-interest at lists.cs.ucla.edu>
>>>>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> 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: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170328/e378dfe0/attachment-0001.html>

From shijunxiao at email.arizona.EDU  Tue Mar 28 14:56:55 2017
From: shijunxiao at email.arizona.EDU (Junxiao Shi)
Date: Tue, 28 Mar 2017 14:56:55 -0700
Subject: [Ndn-interest] NDN packet size
In-Reply-To: <c47ef76d-2e4d-8adf-7547-46c81197158c@cs.arizona.edu>
References: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
	<62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
	<CAOYiq11A5XFgy2wa5ksagp5vDb2fjSVkJpM7=0EfAZHVFLs8QA@mail.gmail.com>
	<d11e8e5c-717b-4b8e-8b8d-b3cf87b8485a@EMHUB6.ad.ucla.edu>
	<CAOYiq11rJ_cocQgcRrG++N7OUED6va+xGA_E87C0gM-vW+jBkw@mail.gmail.com>
	<D5001BB3.3AE47%jefft0@remap.ucla.edu>
	<27D01C90-0661-4189-A2AF-E6526A9E7F59@cs.ucla.edu>
	<c47ef76d-2e4d-8adf-7547-46c81197158c@cs.arizona.edu>
Message-ID: <CAOFH+ObU9Qcnr+k6bqbWP7Ewg2OB44sJr0JPtR9-mDjz9Un9Yw@mail.gmail.com>

Hi Klaus

The setting of 8800 octets is indeed based on the reasons given by Nick
Briggs, which he posted to CCNx mailing list years ago. But that doesn't
answer why 8800 octets is a limit in the code rather than a recommendation.

The reason for having the practical limit is to reduce memory usage.
To receive a packet via socket API, NFD needs to allocate a buffer before
asking the kernel to copy the packet into this buffer. Since the packet
size is unknown at that time, NFD allocates a buffer of 8800 octets.
After the packet is received, assuming it is not fragmented by NDNLP, the
buffer stays around as long as the packet is needed (in PIT or CS), even if
the packet is much smaller than 8800 octets. The alternative would be
truncating the buffer to fit the actual packet size, but that involves
another copying, and we decide to save a copying at the expense of wasting
some memory (the difference between 8800 octets and the actual packet size).
Suppose we increase the practical limit to 1MB, NFD would allocate a 1MB
packet before receiving a packet. If most packets we are dealing with is
much smaller than 1MB, a lot of memory will be wasted.

Yours, Junxiao

On Tue, Mar 28, 2017 at 2:40 PM, Nick Briggs <nicholas.h.briggs at gmail.com>
wrote:

> It gets you 8K bytes of data along with necessary metadata and a name that
> isn't too long in a Content packet.
> It can be encapsulated in a UDP packet with about 6 fragments when you're
> do IP encapsulation. (max UDP is 64K bytes)
> It fits within a 9000 byte jumbo ethernet frame if you're doing direct
> ethernet encapsulation.
>
> -- Nick Briggs
>

On Tue, Mar 28, 2017 at 2:35 PM, Klaus Schneider <klaus at cs.arizona.edu>
wrote:

> Btw, what was the reason for setting the default max packet size to 8800
> in the first place?
>
> Is there any drawback to increasing the default, to let's say 1 Megabyte?
>
> Best regards,
> Klaus
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170328/004e262d/attachment.html>

From nano at remap.UCLA.EDU  Tue Mar 28 15:30:22 2017
From: nano at remap.UCLA.EDU (Alex Horn)
Date: Tue, 28 Mar 2017 17:30:22 -0500
Subject: [Ndn-interest] NDN packet size
In-Reply-To: <CAOFH+ObU9Qcnr+k6bqbWP7Ewg2OB44sJr0JPtR9-mDjz9Un9Yw@mail.gmail.com>
References: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
	<62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
	<CAOYiq11A5XFgy2wa5ksagp5vDb2fjSVkJpM7=0EfAZHVFLs8QA@mail.gmail.com>
	<d11e8e5c-717b-4b8e-8b8d-b3cf87b8485a@EMHUB6.ad.ucla.edu>
	<CAOYiq11rJ_cocQgcRrG++N7OUED6va+xGA_E87C0gM-vW+jBkw@mail.gmail.com>
	<D5001BB3.3AE47%jefft0@remap.ucla.edu>
	<27D01C90-0661-4189-A2AF-E6526A9E7F59@cs.ucla.edu>
	<c47ef76d-2e4d-8adf-7547-46c81197158c@cs.arizona.edu>
	<CAOFH+ObU9Qcnr+k6bqbWP7Ewg2OB44sJr0JPtR9-mDjz9Un9Yw@mail.gmail.com>
Message-ID: <CALqQCKsZRsEd7FXLLk+fPAFNjQD=3Fv4x5e14-kaC6BEObALTg@mail.gmail.com>

I will also add that if you're doing UDP, and want consistency over the
existing internet - I'd suggest 4k, as any UDP packets larger than that
risk being filtered by existing IP-based systems

IE - early testbed ndnvideo app box would not route to UIUC app box unless
packet size was 3800 bytes (enough for 4k overhead)



On Tue, Mar 28, 2017 at 4:56 PM, Junxiao Shi <shijunxiao at email.arizona.edu>
wrote:

> Hi Klaus
>
> The setting of 8800 octets is indeed based on the reasons given by Nick
> Briggs, which he posted to CCNx mailing list years ago. But that doesn't
> answer why 8800 octets is a limit in the code rather than a recommendation.
>
> The reason for having the practical limit is to reduce memory usage.
> To receive a packet via socket API, NFD needs to allocate a buffer before
> asking the kernel to copy the packet into this buffer. Since the packet
> size is unknown at that time, NFD allocates a buffer of 8800 octets.
> After the packet is received, assuming it is not fragmented by NDNLP, the
> buffer stays around as long as the packet is needed (in PIT or CS), even if
> the packet is much smaller than 8800 octets. The alternative would be
> truncating the buffer to fit the actual packet size, but that involves
> another copying, and we decide to save a copying at the expense of wasting
> some memory (the difference between 8800 octets and the actual packet size).
> Suppose we increase the practical limit to 1MB, NFD would allocate a 1MB
> packet before receiving a packet. If most packets we are dealing with is
> much smaller than 1MB, a lot of memory will be wasted.
>
> Yours, Junxiao
>
> On Tue, Mar 28, 2017 at 2:40 PM, Nick Briggs <nicholas.h.briggs at gmail.com>
> wrote:
>
>> It gets you 8K bytes of data along with necessary metadata and a name
>> that isn't too long in a Content packet.
>> It can be encapsulated in a UDP packet with about 6 fragments when you're
>> do IP encapsulation. (max UDP is 64K bytes)
>> It fits within a 9000 byte jumbo ethernet frame if you're doing direct
>> ethernet encapsulation.
>>
>> -- Nick Briggs
>>
>
> On Tue, Mar 28, 2017 at 2:35 PM, Klaus Schneider <klaus at cs.arizona.edu>
> wrote:
>
>> Btw, what was the reason for setting the default max packet size to 8800
>> in the first place?
>>
>> Is there any drawback to increasing the default, to let's say 1 Megabyte?
>>
>> Best regards,
>> Klaus
>>
>
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170328/ce30f334/attachment.html>

From susmit at cs.colostate.edu  Tue Mar 28 17:52:15 2017
From: susmit at cs.colostate.edu (Susmit)
Date: Tue, 28 Mar 2017 18:52:15 -0600
Subject: [Ndn-interest] NDN packet size
In-Reply-To: <CALqQCKsZRsEd7FXLLk+fPAFNjQD=3Fv4x5e14-kaC6BEObALTg@mail.gmail.com>
References: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
	<62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
	<CAOYiq11A5XFgy2wa5ksagp5vDb2fjSVkJpM7=0EfAZHVFLs8QA@mail.gmail.com>
	<d11e8e5c-717b-4b8e-8b8d-b3cf87b8485a@EMHUB6.ad.ucla.edu>
	<CAOYiq11rJ_cocQgcRrG++N7OUED6va+xGA_E87C0gM-vW+jBkw@mail.gmail.com>
	<D5001BB3.3AE47%jefft0@remap.ucla.edu>
	<27D01C90-0661-4189-A2AF-E6526A9E7F59@cs.ucla.edu>
	<c47ef76d-2e4d-8adf-7547-46c81197158c@cs.arizona.edu>
	<CAOFH+ObU9Qcnr+k6bqbWP7Ewg2OB44sJr0JPtR9-mDjz9Un9Yw@mail.gmail.com>
	<CALqQCKsZRsEd7FXLLk+fPAFNjQD=3Fv4x5e14-kaC6BEObALTg@mail.gmail.com>
Message-ID: <CAM4XVkqkWGd3-JQJsLXkcopRgGKCHL80mv+2Lenu56cdApKjyA@mail.gmail.com>

Not much to add here but we did some experiments with large packet sizes. I
am currently uploading a tech report on the NDN website, I will send out a
link when it's uploaded.

In theory, you should only need to change the NDN_MAX_PACKET_SIZE in
tlv.hpp. I have tested this with packets that were several hundred
Megabytes, so I can confirm that large packets work with current
implementation. I have not tested ndn-tools, so there might be a bug there.
If so, please open a bug report in redmine.

The primary benefit of large packet sizes are overall lower packet signing
and verification cost. This will provide better throughput benefit up to
some large packet size and then remain pretty constant. But as others
mentioned before, memory consumption needs to be taken into account - this
will increase linearly with packet size. Packet processing time will also
increase linearly with packet size.

As for UDP limit on linux, it seems pretty large -

$ sysctl net.unix.max_dgram_qlen
net.unix.max_dgram_qlen = 512

$ sysctl net.core.wmem_max
net.core.wmem_max = 134217728

$ sysctl net.core.rmem_max
net.core.rmem_max = 134217728

Thanks.

On Tue, Mar 28, 2017 at 4:30 PM, Alex Horn <nano at remap.ucla.edu> wrote:

> I will also add that if you're doing UDP, and want consistency over the
> existing internet - I'd suggest 4k, as any UDP packets larger than that
> risk being filtered by existing IP-based systems
>
> IE - early testbed ndnvideo app box would not route to UIUC app box unless
> packet size was 3800 bytes (enough for 4k overhead)
>
>
>
> On Tue, Mar 28, 2017 at 4:56 PM, Junxiao Shi <shijunxiao at email.arizona.edu
> > wrote:
>
>> Hi Klaus
>>
>> The setting of 8800 octets is indeed based on the reasons given by Nick
>> Briggs, which he posted to CCNx mailing list years ago. But that doesn't
>> answer why 8800 octets is a limit in the code rather than a recommendation.
>>
>> The reason for having the practical limit is to reduce memory usage.
>> To receive a packet via socket API, NFD needs to allocate a buffer before
>> asking the kernel to copy the packet into this buffer. Since the packet
>> size is unknown at that time, NFD allocates a buffer of 8800 octets.
>> After the packet is received, assuming it is not fragmented by NDNLP, the
>> buffer stays around as long as the packet is needed (in PIT or CS), even if
>> the packet is much smaller than 8800 octets. The alternative would be
>> truncating the buffer to fit the actual packet size, but that involves
>> another copying, and we decide to save a copying at the expense of wasting
>> some memory (the difference between 8800 octets and the actual packet size).
>> Suppose we increase the practical limit to 1MB, NFD would allocate a 1MB
>> packet before receiving a packet. If most packets we are dealing with is
>> much smaller than 1MB, a lot of memory will be wasted.
>>
>> Yours, Junxiao
>>
>> On Tue, Mar 28, 2017 at 2:40 PM, Nick Briggs <nicholas.h.briggs at gmail.com
>> > wrote:
>>
>>> It gets you 8K bytes of data along with necessary metadata and a name
>>> that isn't too long in a Content packet.
>>> It can be encapsulated in a UDP packet with about 6 fragments when
>>> you're do IP encapsulation. (max UDP is 64K bytes)
>>> It fits within a 9000 byte jumbo ethernet frame if you're doing direct
>>> ethernet encapsulation.
>>>
>>> -- Nick Briggs
>>>
>>
>> On Tue, Mar 28, 2017 at 2:35 PM, Klaus Schneider <klaus at cs.arizona.edu>
>> wrote:
>>
>>> Btw, what was the reason for setting the default max packet size to 8800
>>> in the first place?
>>>
>>> Is there any drawback to increasing the default, to let's say 1 Megabyte?
>>>
>>> Best regards,
>>> Klaus
>>>
>>
>> _______________________________________________
>> 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
>
>


-- 

Regards,
Susmit

====================================
http://www.cs.colostate.edu/~susmit
====================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170328/df2965a0/attachment-0001.html>

From susmit at cs.colostate.edu  Tue Mar 28 18:00:13 2017
From: susmit at cs.colostate.edu (Susmit)
Date: Tue, 28 Mar 2017 19:00:13 -0600
Subject: [Ndn-interest] NDN packet size
In-Reply-To: <CAM4XVkqkWGd3-JQJsLXkcopRgGKCHL80mv+2Lenu56cdApKjyA@mail.gmail.com>
References: <CAOYiq129_wozQPMGXkv7HHCAqfCqGa-HkOrJ0Dntg=KK6YpVVA@mail.gmail.com>
	<62CB26F7-EA98-489F-9C91-6E0E89DEDF18@cs.ucla.edu>
	<CAOYiq11A5XFgy2wa5ksagp5vDb2fjSVkJpM7=0EfAZHVFLs8QA@mail.gmail.com>
	<d11e8e5c-717b-4b8e-8b8d-b3cf87b8485a@EMHUB6.ad.ucla.edu>
	<CAOYiq11rJ_cocQgcRrG++N7OUED6va+xGA_E87C0gM-vW+jBkw@mail.gmail.com>
	<D5001BB3.3AE47%jefft0@remap.ucla.edu>
	<27D01C90-0661-4189-A2AF-E6526A9E7F59@cs.ucla.edu>
	<c47ef76d-2e4d-8adf-7547-46c81197158c@cs.arizona.edu>
	<CAOFH+ObU9Qcnr+k6bqbWP7Ewg2OB44sJr0JPtR9-mDjz9Un9Yw@mail.gmail.com>
	<CALqQCKsZRsEd7FXLLk+fPAFNjQD=3Fv4x5e14-kaC6BEObALTg@mail.gmail.com>
	<CAM4XVkqkWGd3-JQJsLXkcopRgGKCHL80mv+2Lenu56cdApKjyA@mail.gmail.com>
Message-ID: <CAM4XVkrFGcRUYm=J93dLFjyukdctX9QmcJfnH2HqkndGdPDF4g@mail.gmail.com>

Sorry, small clarification:

I was looking at a machine that was previously tuned.
Default rmax/wmax for linux is 212992 by on my laptop (Fedora 25,
4.9.14-200.fc25.x86_64).

On Tue, Mar 28, 2017 at 6:52 PM, Susmit <susmit at cs.colostate.edu> wrote:

> Not much to add here but we did some experiments with large packet sizes.
> I am currently uploading a tech report on the NDN website, I will send out
> a link when it's uploaded.
>
> In theory, you should only need to change the NDN_MAX_PACKET_SIZE in
> tlv.hpp. I have tested this with packets that were several hundred
> Megabytes, so I can confirm that large packets work with current
> implementation. I have not tested ndn-tools, so there might be a bug there.
> If so, please open a bug report in redmine.
>
> The primary benefit of large packet sizes are overall lower packet signing
> and verification cost. This will provide better throughput benefit up to
> some large packet size and then remain pretty constant. But as others
> mentioned before, memory consumption needs to be taken into account - this
> will increase linearly with packet size. Packet processing time will also
> increase linearly with packet size.
>
> As for UDP limit on linux, it seems pretty large -
>
> $ sysctl net.unix.max_dgram_qlen
> net.unix.max_dgram_qlen = 512
>
> $ sysctl net.core.wmem_max
> net.core.wmem_max = 134217728
>
> $ sysctl net.core.rmem_max
> net.core.rmem_max = 134217728
>
> Thanks.
>
> On Tue, Mar 28, 2017 at 4:30 PM, Alex Horn <nano at remap.ucla.edu> wrote:
>
>> I will also add that if you're doing UDP, and want consistency over the
>> existing internet - I'd suggest 4k, as any UDP packets larger than that
>> risk being filtered by existing IP-based systems
>>
>> IE - early testbed ndnvideo app box would not route to UIUC app box
>> unless packet size was 3800 bytes (enough for 4k overhead)
>>
>>
>>
>> On Tue, Mar 28, 2017 at 4:56 PM, Junxiao Shi <
>> shijunxiao at email.arizona.edu> wrote:
>>
>>> Hi Klaus
>>>
>>> The setting of 8800 octets is indeed based on the reasons given by Nick
>>> Briggs, which he posted to CCNx mailing list years ago. But that doesn't
>>> answer why 8800 octets is a limit in the code rather than a recommendation.
>>>
>>> The reason for having the practical limit is to reduce memory usage.
>>> To receive a packet via socket API, NFD needs to allocate a buffer
>>> before asking the kernel to copy the packet into this buffer. Since the
>>> packet size is unknown at that time, NFD allocates a buffer of 8800 octets.
>>> After the packet is received, assuming it is not fragmented by NDNLP,
>>> the buffer stays around as long as the packet is needed (in PIT or CS),
>>> even if the packet is much smaller than 8800 octets. The alternative would
>>> be truncating the buffer to fit the actual packet size, but that involves
>>> another copying, and we decide to save a copying at the expense of wasting
>>> some memory (the difference between 8800 octets and the actual packet size).
>>> Suppose we increase the practical limit to 1MB, NFD would allocate a 1MB
>>> packet before receiving a packet. If most packets we are dealing with is
>>> much smaller than 1MB, a lot of memory will be wasted.
>>>
>>> Yours, Junxiao
>>>
>>> On Tue, Mar 28, 2017 at 2:40 PM, Nick Briggs <
>>> nicholas.h.briggs at gmail.com> wrote:
>>>
>>>> It gets you 8K bytes of data along with necessary metadata and a name
>>>> that isn't too long in a Content packet.
>>>> It can be encapsulated in a UDP packet with about 6 fragments when
>>>> you're do IP encapsulation. (max UDP is 64K bytes)
>>>> It fits within a 9000 byte jumbo ethernet frame if you're doing direct
>>>> ethernet encapsulation.
>>>>
>>>> -- Nick Briggs
>>>>
>>>
>>> On Tue, Mar 28, 2017 at 2:35 PM, Klaus Schneider <klaus at cs.arizona.edu>
>>> wrote:
>>>
>>>> Btw, what was the reason for setting the default max packet size to
>>>> 8800 in the first place?
>>>>
>>>> Is there any drawback to increasing the default, to let's say 1
>>>> Megabyte?
>>>>
>>>> Best regards,
>>>> Klaus
>>>>
>>>
>>> _______________________________________________
>>> 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
>>
>>
>
>
> --
>
> Regards,
> Susmit
>
> ====================================
> http://www.cs.colostate.edu/~susmit
> ====================================
>



-- 

Regards,
Susmit

====================================
http://www.cs.colostate.edu/~susmit
====================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170328/83695a89/attachment.html>

From dongqian at cstnet.cn  Fri Mar 31 05:18:18 2017
From: dongqian at cstnet.cn (=?GBK?B?tq3Hqw==?=)
Date: Fri, 31 Mar 2017 20:18:18 +0800 (GMT+08:00)
Subject: [Ndn-interest] Some questions about NDN forwarding and traffic
 control
Message-ID: <e0fad1.f65c.15b244d51ce.Coremail.dongqian@cstnet.cn>

Dear community,


We are NDN beginners from Computer Network Information Center, Chinese Academy of Sciences. We are uncertain about the following issues, will you give us kind help.


As we understand, the first stage is that routing module (NLSR or hyperbolic routing) propagates initial or long term coarse grained Name information, the second stage is that the adaptive forwarding plane obtains real time, precise, and fine grained Name information, so we get the FIB table. When an Interest is sent to a router, if its Name is not in CS or PIT, the router will check FIB and send it to another router (or drop).  On the other hand, Data will be forwarded by checking PIT in an intermidiate router.


And, we have some questions:


1. What principle or mechanism to establish the original FIB? In the traditional TCP/IP network, the routing protocol establishes the RIB depending on the IP address, and the transmission process also uses a IP address. In NDN network, because the Interest forwarding or disseminate is based on name, whether the original FIB establishing is also based on name? For a new content, namely some new Interests with new names, how does the original FIB provide the right or effective interface for forwarding? Using flooding method to detect or maybe some active signals from the new Content located nodes?


2. In Multi-path and Multi-source scenario without considering In-network cache, do we just need to consider about how to divide Interests in consumer's faces? Do Data chunks have any size range? Is it necessory to consider In-network collaborative or non-collaborative cache? 


3. In NDN, intermidiate routers decide how to forward packets, do we need a controller like SDN to propagates Name prefix information to mitigate the scale of FIB/PIT and add global factor?


We appreciate your reply very much.


Best regards.


Dong Qian


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

From lixia at CS.UCLA.EDU  Fri Mar 31 07:37:55 2017
From: lixia at CS.UCLA.EDU (Lixia Zhang)
Date: Fri, 31 Mar 2017 07:37:55 -0700
Subject: [Ndn-interest] Some questions about NDN forwarding and traffic
 control
In-Reply-To: <e0fad1.f65c.15b244d51ce.Coremail.dongqian@cstnet.cn>
References: <e0fad1.f65c.15b244d51ce.Coremail.dongqian@cstnet.cn>
Message-ID: <C3FED170-5F33-4517-AFFF-FFA7BFE07A06@cs.ucla.edu>


> On Mar 31, 2017, at 5:18 AM, ?? <dongqian at cstnet.cn> wrote:
> 
> Dear community,
> 
> We are NDN beginners from Computer Network Information Center, Chinese Academy of Sciences. We are uncertain about the following issues, will you give us kind help.

thanks for your interest in looking into NDN.

> As we understand, the first stage is that routing module (NLSR or hyperbolic routing) propagates initial or long term coarse grained Name information, the second stage is that the adaptive forwarding plane obtains real time, precise, and fine grained Name information, so we get the FIB table.

I am not sure I fully understand the above description.. .
Think this way:
1/ the fundamental job of networking is to fetch the data pieces being requested by all consumers.

2/ FIB is one of the components in a forwarder helping achieve that goal.
Do note that it is the forwarding strategy that makes the forwarding decision, using FIB as one of the inputs.

3/ FIB can be populated by one or multiple routing protocols; FIB entries may also be filled by other means.

As we move forward with NDN research over the last few years, our understanding of NDN forwarding also advances.  You might be interested in checking out a few writeups, starting from section 2 in NDN TR#1 <https://named-data.net/wp-content/uploads/TR001ndn-proj.pdf> (back in 2010), stateful forwarding (2013) <http://named-data.net/publications/comcom-stateful-forwarding/>, the role of routing in NDN (2014) <http://named-data.net/publications/role_of_routing_ndn/>, etc.


> When an Interest is sent to a router, if its Name is not in CS or PIT, the router will check FIB and send it to another router (or drop).

Please see pointer 2/ in the above.

> On the other hand, Data will be forwarded by checking PIT in an intermidiate router.
> 
> And, we have some questions:
> 
> 1. What principle or mechanism to establish the original FIB? In the traditional TCP/IP network, the r! outing pr otocol establishes the RIB depending on the IP address, and the transmission process also uses a IP address. In NDN network, because the Interest forwarding or disseminate is based on name, whether the original FIB establishing is also based on name?

this question suggests that you may want to start with NDN TR#1 I mentioned in the above.

> For a new content, namely some new Interests with new names, how does the original FIB provide the right or effective interface for forwarding?

A similar question: when my department adds a new host, how would all routers know how to forward packets to it?

> Using flooding method to detect or maybe some active signals from the new Content located nodes?
> 
> 2. In Multi-path and Multi-source scenario without considering In-network cache, do we just need to consider about how to divide Interests in consumer's faces?

you may want to check out the stateful forwarding paper mentioned above.

> Do Data chunks have any size range? Is it necessory to consider In-network collaborative or non-collaborative cache? 

People have built a big literature in NDN caching, Google can help find the papers.

> 3. In NDN, intermidiate routers decide how to forward packets, do we need a controller like SDN to propagates Name prefix information to mitigate the scale of FIB/! PIT and a dd global factor?

- As I have heard, there seem multiple people investigating into SDN-NDN relations.
- there are multiple ways to mitigate FIB scaling issue

my 2 cents,
Lixia

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

From lanwang at memphis.edu  Fri Mar 31 16:56:48 2017
From: lanwang at memphis.edu (Lan Wang (lanwang))
Date: Fri, 31 Mar 2017 23:56:48 +0000
Subject: [Ndn-interest] Some questions about NDN forwarding and traffic
 control
In-Reply-To: <e0fad1.f65c.15b244d51ce.Coremail.dongqian@cstnet.cn>
References: <e0fad1.f65c.15b244d51ce.Coremail.dongqian@cstnet.cn>
Message-ID: <9D9D2AA8-16EA-43CD-B68E-25ED2CD55029@memphis.edu>



On Mar 31, 2017, at 7:18 AM, ?? <dongqian at cstnet.cn<mailto:dongqian at cstnet.cn>> wrote:

Dear community,

We are NDN beginners from Computer Network Information Center, Chinese Academy of Sciences. We are uncertain about the following issues, will you give us kind help.

As we understand, the first stage is that routing module (NLSR or hyperbolic routing) propagates initial or long term coarse grained Name information, the second stage is that the adaptive forwarding plane obtains real time, precise, and fine grained Name information, so we get the FIB table. When an Interest is sent to a router, if its Name is not in CS or PIT, the router will check FIB and send it to another router (or drop).  On the other hand, Data will be forwarded by checking PIT in an intermidiate router.

And, we have some questions:

1. What principle or mechanism to establish the original FIB? In the traditional TCP/IP network, the r! outing pr otocol establishes the RIB depending on the IP address, and the transmission process also uses a IP address. In NDN network, because the Interest forwarding or disseminate is based on name, whether the original FIB establishing is also based on name? For a new content, namely some new Interests with new names, how does the original FIB provide the right or effective interface for forwarding? Using flooding method to detect or maybe some active signals from the new Content located nodes?

The FIB establishment is also based on name.  To establish the FIB entry for a new name prefix, you can use a name based routing protocol such as NLSR (https://named-data.net/publications/techreports/ndn-0037-1-nlsr/) or hyperbolic routing (https://named-data.net/publications/techreports/ndn-0042-1-asf/).  Flooding would work but is not efficient in most cases.

Lan

2. In Multi-path and Multi-source scenario without considering In-network cache, do we just need to consider about how to divide Interests in consumer's faces? Do Data chunks have any size range? Is it necessory to consider In-network collaborative or non-collaborative cache?

3. In NDN, intermidiate routers decide how to forward packets, do we need a controller like SDN to propagates Name prefix information to mitigate the scale of FIB/! PIT and a dd global factor?

We appreciate your reply very much.

Best regards.

Dong Qian



_______________________________________________
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu<mailto:Ndn-interest at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest

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

From dongqian at cstnet.cn  Fri Mar 31 19:14:06 2017
From: dongqian at cstnet.cn (=?utf-8?B?6JGj6LCm?=)
Date: Sat, 1 Apr 2017 10:14:06 +0800 (GMT+08:00)
Subject: [Ndn-interest] Some questions about NDN forwarding and traffic
 control
In-Reply-To: <C3FED170-5F33-4517-AFFF-FFA7BFE07A06@cs.ucla.edu>
References: <e0fad1.f65c.15b244d51ce.Coremail.dongqian@cstnet.cn>
	<C3FED170-5F33-4517-AFFF-FFA7BFE07A06@cs.ucla.edu>
Message-ID: <1b0acad.260a0.15b274a82f4.Coremail.dongqian@cstnet.cn>

Dear Prof. Zhang,


Thank you very much for your reply and tips. We will think about it deeply according to these papers.

Best wishes,


Dong Qian


-----????-----
???: "Lixia Zhang" <lixia at cs.ucla.edu>
????: 2017?3?31? ???
???: "??" <dongqian at cstnet.cn>
??: ndn-interest at lists.cs.ucla.edu, "???" <shishanshan at cstnet.cn>
??: Re: [Ndn-interest] Some questions about NDN forwarding and traffic control



On Mar 31, 2017, at 5:18 AM, ?? <dongqian at cstnet.cn> wrote:


Dear community,


We are NDN beginners from Computer Network Information Center, Chinese Academy of Sciences. We are uncertain about the following issues, will you give us kind help.


thanks for your interest in looking into NDN.


As we understand, the first stage is that routing module (NLSR or hyperbolic routing) propagates initial or long term coarse grained Name information, the second stage is that the adaptive forwarding plane obtains real time, precise, and fine grained Name information, so we get the FIB table.


I am not sure I fully understand the above description.. .
Think this way:
1/ the fundamental job of networking is to fetch the data pieces being requested by all consumers.


2/ FIB is one of the components in a forwarder helping achieve that goal.
Do note that it is the forwarding strategy that makes the forwarding decision, using FIB as one of the inputs.


3/ FIB can be populated by one or multiple routing protocols; FIB entries may also be filled by other means.


As we move forward with NDN research over the last few years, our understanding of NDN forwarding also advances.  You might be interested in checking out a few writeups, starting from section 2 in NDN TR#1 (back in 2010), stateful forwarding (2013), the role of routing in NDN (2014), etc.




When an Interest is sent to a router, if its Name is not in CS or PIT, the router will check FIB and send it to another router (or drop).


Please see pointer 2/ in the above.


On the other hand, Data will be forwarded by checking PIT in an intermidiate router.


And, we have some questions:


1. What principle or mechanism to establish the original FIB? In the traditional TCP/IP network, the r! outing pr otocol establishes the RIB depending on the IP address, and the transmission process also uses a IP address. In NDN network, because the Interest forwarding or disseminate is based on name, whether the original FIB establishing is also based on name?


this question suggests that you may want to start with NDN TR#1 I mentioned in the above.


For a new content, namely some new Interests with new names, how does the original FIB provide the right or effective interface for forwarding?


A similar question: when my department adds a new host, how would all routers know how to forward packets to it?


Using flooding method to detect or maybe some active signals from the new Content located nodes?


2. In Multi-path and Multi-source scenario without considering In-network cache, do we just need to consider about how to divide Interests in consumer's faces?


you may want to check out the stateful forwarding paper mentioned above.


Do Data chunks have any size range? Is it necessory to consider In-network collaborative or non-collaborative cache? 


People have built a big literature in NDN caching, Google can help find the papers.


3. In NDN, intermidiate routers decide how to forward packets, do we need a controller like SDN to propagates Name prefix information to mitigate the scale of FIB/! PIT and a dd global factor?


- As I have heard, there seem multiple people investigating into SDN-NDN relations.
- there are multiple ways to mitigate FIB scaling issue


my 2 cents,
Lixia




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

From dongqian at cstnet.cn  Fri Mar 31 19:15:22 2017
From: dongqian at cstnet.cn (=?utf-8?B?6JGj6LCm?=)
Date: Sat, 1 Apr 2017 10:15:22 +0800 (GMT+08:00)
Subject: [Ndn-interest] Some questions about NDN forwarding and traffic
 control
In-Reply-To: <9D9D2AA8-16EA-43CD-B68E-25ED2CD55029@memphis.edu>
References: <e0fad1.f65c.15b244d51ce.Coremail.dongqian@cstnet.cn>
	<9D9D2AA8-16EA-43CD-B68E-25ED2CD55029@memphis.edu>
Message-ID: <160c398.260d3.15b274bade0.Coremail.dongqian@cstnet.cn>

Dear Prof. Wang,


Thank you very much for your reply and tips. We will think about it deeply according to these papers.

Best wishes,


Dong Qian



-----????-----
???: "Lan Wang (lanwang)" <lanwang at memphis.edu>
????: 2017?4?1? ???
???: "??" <dongqian at cstnet.cn>
??: "ndn-interest at lists.cs.ucla.edu" <ndn-interest at lists.cs.ucla.edu>, "???" <shishanshan at cstnet.cn>
??: Re: [Ndn-interest] Some questions about NDN forwarding and traffic control






On Mar 31, 2017, at 7:18 AM, ?? <dongqian at cstnet.cn> wrote:


Dear community,


We are NDN beginners from Computer Network Information Center, Chinese Academy of Sciences. We are uncertain about the following issues, will you give us kind help.


As we understand, the first stage is that routing module (NLSR or hyperbolic routing) propagates initial or long term coarse grained Name information, the second stage is that the adaptive forwarding plane obtains real time, precise, and fine grained Name information, so we get the FIB table. When an Interest is sent to a router, if its Name is not in CS or PIT, the router will check FIB and send it to another router (or drop).  On the other hand, Data will be forwarded by checking PIT in an intermidiate router.


And, we have some questions:


1. What principle or mechanism to establish the original FIB? In the traditional TCP/IP network, the r! outing pr otocol establishes the RIB depending on the IP address, and the transmission process also uses a IP address. In NDN network, because the Interest forwarding or disseminate is based on name, whether the original FIB establishing is also based on name? For a new content, namely some new Interests with new names, how does the original FIB provide the right or effective interface for forwarding? Using flooding method to detect or maybe some active signals from the new Content located nodes?


The FIB establishment is also based on name.  To establish the FIB entry for a new name prefix, you can use a name based routing protocol such as NLSR (https://named-data.net/publications/techreports/ndn-0037-1-nlsr/) or hyperbolic routing (https://named-data.net/publications/techreports/ndn-0042-1-asf/).  Flooding would work but is not efficient in most cases.  


Lan


2. In Multi-path and Multi-source scenario without considering In-network cache, do we just need to consider about how to divide Interests in consumer's faces? Do Data chunks have any size range? Is it necessory to consider In-network collaborative or non-collaborative cache? 


3. In NDN, intermidiate routers decide how to forward packets, do we need a controller like SDN to propagates Name prefix information to mitigate the scale of FIB/! PIT and a dd global factor?


We appreciate your reply very much.


Best regards.


Dong Qian



_______________________________________________
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu
http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest





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