SigMgr::stNULL does not match NDN specifications about dct HOT 3 CLOSED

This doesn't mean what you think it does. It's used to denote a NULL signature manager NOT a signature. That number and signature should NEVER be in a packet. In sigmgr_null.hpp, the comment header:

• SigMgr Null provides a signing and validation methods that do nothing.
• This is specifically provided for cert distribution and should not be
• used otherwise (i.e., if you don't know why you are using this, don't!).

At the link you provided, the Null Signature Type is expressly described as "Empty signature for testing and experimentation" which is absolutely not the intent of SigMgrNULL at all. It is used to keep from changing the signature of a cert that is already signed.

from dct.

This doesn't mean what you think it does. It's used to denote a NULL signature manager NOT a signature.

This contradicts the comment directly above the code, which labels these constants as SigTypes and indicates that they should match NDN assigned numbers.

from dct.

I'm not sure where you are finding the words "should match NDN assigned numbers" There is the above-cited comment in sigmgr_null.hpp. There is a not about the "'null' signer (no signature added to data)" in sigmgr.hpp. Again, that "type" never goes on the wire. The only reason for compatibility with NDN assigned numbers is to avoid any conflicts.

from dct.