Project

General

Profile

Actions
Copy link

Task #2040

closed

ndn-autoconfig: remote prefix registration

Added by Junxiao Shi about 10 years ago. Updated about 10 years ago.

Status:
Abandoned
Priority:
Normal
Assignee:
-
Category:
Tools
Target version:
v0.3
Start date:
Due date:
% Done:

0%

Estimated time:
3.00 h

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.

Related issues 1 (0 open — 1 closed)

Blocks NFD - Task #2041: HUB discovery scenario: remote prefix registrationAbandoned

Actions
Actions
Copy link
 #1

Updated by Junxiao Shi about 10 years ago

  • Blocked by Task #2039: Controller: remote prefix registration added
Actions
Copy link
 #2

Updated by Junxiao Shi about 10 years ago

  • Blocks Task #2041: HUB discovery scenario: remote prefix registration added
Actions
Copy link
 #3

Updated by Junxiao Shi about 10 years ago

  • Blocked by deleted (Task #2039: Controller: remote prefix registration)
Actions
Copy link
 #4

Updated by Junxiao Shi about 10 years ago

  • 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.
Actions
Copy link

Also available in: Atom PDF