Feature #3144
closed
RibMgmt: routable-prefixes
100%
Description
In RibMgmt protocol, declare <prefix>/rib/routable-prefixes as a StatusDataset that contains the routable prefixes of a host.
Updated by Junxiao Shi over 9 years ago
A prefix is a "routable prefix" if: after an application on the local host registers a prefix under a routable prefix, an Interest expressed on other hosts (typically globally) should be able to reach this host.
Routable prefixes of a router are announced by this router into the global routing system.
Routable prefixes of an end host are the intersection of the routable prefixes of connected gateway routers and the prefixes this end host is able to register onto the router.
For example, an end host that is connected to /ndn/edu/arizona and /ndn/edu/memphis, and has certificates to register /ndn/edu/arizona/user and /ndn/guest/user would have routable prefixes {/ndn/edu/arizona/user}.
Updated by Junxiao Shi over 9 years ago
- Blocks Feature #3145: Collect and publish routable-prefixes added
Updated by Junxiao Shi over 8 years ago
- % Done changed from 0 to 50
RibMgmt r18 defines routable-prefixes dataset according to note-1 definition.
Currently each entry is simply a Name.
I wonder whether an additional state field would be useful. Its possible values are:
- Advertisable: This prefix can be advertised if a producer registers a prefix under it.
- Advertising: This prefix is being advertised but routing is not converged or AutoPrefixPropagation is still in progress.
- Advertised: This prefix is advertised and routing has converged or AutoPrefixPropagation has completed.
- Unavailable: This prefix is advertisable, but the last advertising attempt has failed (i.e. AutoPrefixPropagation has failed); another attempt will be made.
On a router with NLSR, all routable prefixes should be Advertising or Advertised.
On an end host with AutoPrefixPropagation, all four states are possible.
If we adopt a state field, a notification stream that indicates state changes would also be useful. It allows a producer to monitor the progress of AutoPrefixPropagation.
Updated by Junxiao Shi over 8 years ago
- Status changed from In Progress to Resolved
- % Done changed from 50 to 100
20160823 call points out that with NLSR, it's impossible to distinguish whether "routing has converged" unless you explicitly ask every router in the global network.
Thus, the four states are applicable to end hosts with AutoPrefixPropagation only.
20160825 call decides that the state field is unnecessary.
Therefore, this design is now complete.
Updated by Junxiao Shi about 8 years ago
- Status changed from Resolved to Closed
Closing because there's no objection.