Feature #3824
Updated by Junxiao Shi about 8 years ago
Currently NetworkRegionTable API is implemented only provides for providing means to determine forwarding behavior of nfd in processing incoming Interests incommingInterest with Link objects. However, for objects attached. For supporting mobility, which is the mentioned goal of this table, it seems there should be a mobile producer to generate a Link object, it's also necessary mechanism for the application clients to learn retrieve Region Name(s) of local router which the region names assigned client is connected to. Something similar to the local NFD, which hub discovery. In simulation one can be used easily have an application to derive delegation names. This information shall be exposed as respond interest with data containing NRT entries. But maybe we should have a [[StatusDataset]]. standard way of this exchange in nfd level. We could extend the API first to provide means for retrieving Region Name(s) in one Data pkt.