Feature #2237
Updated by Junxiao Shi over 7 years ago
The certificate signing a signed the remote registration command may be available only at the machine issuing the command. This creates a chicken-and-egg problem: to verify command NFD-RIB NRD needs to fetch the cert, to fetch the cert the prefix should be already registered. To This task is to solve this problem: NFD-RIB's validator problem in the following way: **Input**: receive remote registration command for *PREFIX* **Actions**: During validation, any certificate with the name starting with *PREFIX* should send two Interests at be fetched using `LocalControlHeader::setOutgoingFaceId()` Current **prerequisites**: During registration, strategy for the same time, first one prefix needs to the requester (using NextHopFaceId) and second one be changed to the infrastructure (without NextHopFaceId). `client-control`.