Task #1719
closed
RibMgmt: Origin for remote and automatic registration
100%
Description
RibMgmt Origin field has these choices currently: static, nlsr, app.
However, none of these choices fits the following scenarios:
- a laptop connects to a HUB, and it sends a prefix registration command to the HUB (using
ndn:/localhop/nfd/ribprefix) - a laptop connects to a HUB, and the
nfd-autoregserver on a HUB automatically registers a Route toward the laptop - a laptop connects to a HUB, and the
ndn-autoconftool registers a prefix toward the HUB
This Task proposes to define three additional values for Origin field:
- client: indicates a Route toward a client node attached to this router, installed via remote registration
- autoreg: indicates a Route toward a client node attached to this router, registered automatically by this router
- autoconf: indicates a Route toward a HUB from the laptop, registered automatically by the
ndn-autoconftool
Updated by Junxiao Shi almost 10 years ago
- Blocks Bug #1710: nfd-autoreg uses FIB management protocol instead of RIB management added
Updated by Junxiao Shi almost 10 years ago
- Priority changed from Normal to Urgent
I plan to use these numerical codes:
- client=65
- autoreg=64
I'll work on this Task once the proposal is approved.
Updated by Alex Afanasyev almost 10 years ago
Numbers seem fine. The only change I would do is rename "client" to "autoconf", so it reflects who exactly created the entries (client is too broad).
Updated by Junxiao Shi almost 10 years ago
autoconf isn't a good choice, because we haven't decided ndn-autoconf shall perform remote registration.
There are other proposals for remote registration, such as letting RIB Daemon or even certain apps on laptop to send remote registration command.
Updated by Alex Afanasyev almost 10 years ago
I'm not sure how autoconf is related to the remote registration. In any case, this name only appears in documentation, so we just need to specify which app (logical process) is responsible for these routes. Numbers are fine and this issue should be closed after origin IDs are documented in the spec.
Updated by Junxiao Shi almost 10 years ago
- Description updated (diff)
autoconf will have numeric code 66.
20140701 conference call approves the proposal after this addition.
Updated by Junxiao Shi almost 10 years ago
- Status changed from New to Resolved
- % Done changed from 0 to 100
RibMgmt revision 7 is updated.
Updated by Junxiao Shi almost 10 years ago
- Status changed from Resolved to Closed
20140701 conference call approved RibMgmt revision 7.