NFD

Can we update prefix reg to use /localhost/nrd/rib for consistency with the existing management protocols? (mostly adding the "rib" module name component)

Also, Alex mentioned preferring "nfd" instead of "nrd". I'm wondering if there's any benefit to leaving it as "nrd" since it is a separate process. Specifically, using the same NRD with different forwarder implementations.

I'll repeat. I don't see the need for adding additional component. The whole purpose of NRD is to manage RIB, there is no other functionality... At least I'm not seeing it right now.

There is no harm in adding, but not quite sure what the benefit is either.

I plan to use namespace: ndn:/localhost/nfd/rib.

Benefits:

• Blur the concept of NRD: RIB Management is part of NFD, although it's implemented in a separate process.
• Detect NRD failure
  1. NFD listens on this namespace with highest cost.
  2. When NRD comes up, its FIB entry will capture all Interests, and nothing would go to NFD's listener.
  3. When NRD dies, its FIB entry is gone.
  4. Next command to NRD will go to NFD's listener, which indicates NRD has failed, and NFD should terminate itself.

20140417 conference call decides that NFD need not fail upon NRD failure. This should be handled by monitoring infrastructure.

NFD can attached a listener that responds StatusCode=503 to ndn:/localhost/nfd/rib when NRD is not there.

Application should treat such 503 error similarly to a bind(2) failure.

In the unregister command, the parameter FaceId is listed as required, but later the description says "If FaceId is omitted or is set to zero, it is implied as the requesting face (self deregistration)." Should FaceId be optional then?

The advertise/withdraw commands are for the operator or a routing protocol to inject a prefix into another routing protocol. For example, the operator may specify in a configuration file that the prefix /ndn/edu/memphis should be advertised by NLSR to other nodes. Then the program that parses this configuration file should generate an advertise command Interest to NRD including the prefix and protocol (NLSR) in this case. The operator may also use command-line tool (e.g. nfdc) to issue the advertise and withdraw commands to NRD.