NFD

I knew nothing about NFD mgmt before, I am reading NFD developer guide "Management" section, NFD Management Protocol on Wiki page, and the source code. Are there any other materials I could refer to? Thanks!

Not that I know of.

Just want to make sure I am on the correct direction before changing the code.

To "include nexthop record’s endpoint ID in status dataset", I need to:

1. In ndn-cxx/ndn-cxx/mgmt/nfd/fib-entry.hpp, add a "m_endpointID" private field and corresponding get and set methond. And modify the fib-entry.cpp file.
2. In NFD/daemon/mgmt/fib-manager.cpp, at line 128, add "setEndpointID(...)"

Two equal NextHopRecords should have the same EndpointId, right?

Yes.

FibMgmt rev41 assigns 0x71 to EndpointId in dataset. Any reason not to use a number in application range, i.e. 0x80 or above?

No, there is no reason. I don't know there is a range requirement. Do I need to reassign a value?

Junxiao Shi wrote:

FibMgmt rev41 assigns 0x71 to EndpointId in dataset. Any reason not to use a number in application range, i.e. 0x80 or above?

A lot of type assignments in NFD mgmt protocol already use numbers below 0x80, I don't see the problem.

A lot of type assignments in NFD mgmt protocol already use numbers below 0x80, I don't see the problem.

So far, only TLV-TYPEs in ControlCommand use [101, 127] range. Otherwise, they use application range.

https://gerrit.named-data.net/5463 patchset4 displays FaceId+EndpointId as:

faceid=262 (endpointId=1, cost=9)

This is not quite right, because FaceId and EndpointId together identify a nexthop, while cost is an attribute of the nexthop.

The syntax should be:

face=262~1 (cost=9)

The syntax should be:

face=262~1 (cost=9)

Should we omit the EndpointID if it's 0, like
face=262 (cost=9)

Should we omit the EndpointID if it's 0, like
face=262 (cost=9)

Yes, that's fine.

These changes have been reverted, see #4973.