[Mini-NDN] Controller implementation in mini-ndn : Request for advice

[Ashlesh Gawande (agawande)]

Yes the controller should still be available via Mininet but it is no longer in the conf_parser for Mini-NDN.



Mini-NDN does have a provision to add switches but I do not know the use case (I think they were added back to support NFD tests at one point).

https://github.com/named-data/mini-ndn/blob/master/ndn/conf_parser.py


And yes Mini-NDN still just uses hosts.


Maybe Jeeva can elaborate why he needs a controller.


Ashlesh

________________________________
From: Junxiao Shi <shijunxiao at email.arizona.edu>
Sent: Monday, June 6, 2016 1:18:04 PM
To: Rajendran Jeeva; Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] Controller implementation in mini-ndn : Request for advice


Dear folks

In Mininet, a Controller is a centralized component that makes forwarding decisions for Ethernet Switches.
I believe that Controller is still available for use in Mini-NDN, because Mini-NDN is now an add-on of Mininet and not a fork.

However, I wonder what's the semantics of a Controller in Mini-NDN?
Last time I looked, Mini-NDN uses only Hosts. Each Host has an NFD and an NLSR instance. They make forwarding decisions in a distributed manner.
Since there is no Switch involved, what's a use case for Controller?

Yours, Junxiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160606/e1215f0a/attachment.html>