Task #2040
closed
ndn-autoconfig: remote prefix registration
Added by Junxiao Shi about 10 years ago.
Updated about 10 years ago.
Description
After connecting to a HUB, register zero or more prefixes via remote prefix registration.
Prefixes to register should be accepted on the command line.
- Blocked by Task #2039: Controller: remote prefix registration added
- Blocks Task #2041: HUB discovery scenario: remote prefix registration added
- Blocked by deleted (Task #2039: Controller: remote prefix registration)
- Status changed from New to Abandoned
20141013 conference call decides that remote prefix registration should be done by nrd, because:
ndn-autoconfig cannot dynamically register new prefixes that applications need.
Sometimes, an application needs to register a prefix out of user identity namespace, if permitted by the trust configuration on the gateway router.nrd already knows what local applications want, and could forward the registrations to the gateway.
Also available in: Atom
PDF
Updated by