NFD » ndn-cxx

What TLV type values should I assign NInNacks and NOutNacks?

It appears that LinkCounters also has NInPackets and NOutPackets counters, so ForwarderStatus and FaceStatus need those as well.

Reply to note-6:

Yes, but not now.

In #3088, don't copy packet counters.

note-7 says packet counters need not be copied into FaceStatus.
Similarly, #3088 could skip copying Nack counters as well.

Therefore, this issue is no longer blocking #3088.

I disagree with note-13.

A correct implementation of a decoding procedure should check nothing extra exists at the end of a parent element, so any changes of a required element would be a breaking change, regardless of where it's placed.

The ordering "NInInterests, NInDatas, NInNacks, NOutInterests, NOutDatas, NOutNacks, NInPackets, NInBytes, NOutPackets, NOutBytes" follows the logical order of "incoming network later counters, outgoing network layer counters, incoming link layer counters, outgoing link layer counters".
The alternate would be a nonsense ordering.

Recommendation for NFD-Android:

• Do not upgrade NFD until the library is ready.
• If the library must support both versions of NFD Management protocol, it may implement the additional field as if it's an optional field.