Feature #3142
Updated by Junxiao Shi over 8 years ago
Make [[RibMgmt]] commands and datasets available under a configurable set of top-level prefixes, in addition to `ndn:/localhost/nfd/rib`.
**Necessity**
Currently, NFD-RIB on a gateway router is configured to accept prefix registration commands under `ndn:/localhop/nfd/rib`, and an end host may send a prefix registration command under this prefix to register a route on the connected gateway router.
However, this procedure would not work if an end host is connected to multiple gateway routers, because the `ndn:/localhop/nfd/rib` prefix cannot effectively distinguish which gateway router should the command be forwarded to.
This issue includes:
* Declare a configuration option to specify top-level prefixes for NFD-RIB.
* The configured values should omit the final `rib` component. For example, `ndn:/localhop/hobo/nfd` causes NFD-RIB to listen on `ndn:/localhop/hobo/nfd/rib` top-level prefix. The purpose is to be compatible with #3141.
* `ndn:/localhost/nfd/rib` is always enabled, and need not appear in the configuration.
* `ndn:/localhop/nfd/rib` is not implicitly enabled. If needed, it should be configured as `ndn:/localhop/nfd`.
* Modify NFD-RIB initialization procedure to add all configured top-level prefixes to the dispatcher.
With this Feature, every gateway router can be configured with a distinct top-level prefix, so that an end host connected to multiple gateway routers would be able to effectively address each gateway router using a different prefix.
Note that this Feature would not allow an end host to discover the top-level prefix of NFD-RIB on a connected gateway router, and that will be solved in #3143. a separate issue.
**NFD Developer Guide** should be updated to reflect the change.