Michael Frey

Hmm, somebody pointed out that ccnx binary protocol is used for communication between ccn-lite-relay and the ccn-lite-ctrl util. I skimmed through ``ccnl_mgmt`` and ``ccnl_mgmt_handle`` which seems to confirm that. Nevertheless,...

Are you going through RIOTs code/packages and check if it really builds for 8 bit or are you considering to use CCN-lite on an 8 bit architecture?

Sounds interesting. Let me know if you're up for a 🍺 in Berlin. There are few challenges with cryptographic operations and ccn-lite

you are referring to the ccnl_{pacet_format}_dehead functions?

Also, ``git grep`` to the rescue, i.e. ```bash $ git grep TODO CMakeLists.txt: set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wextra -Wall -Werror -std=c99 -g -pedantic") #TODO: add -fsanitize=address build-test-helper.sh: # TODO: fix $NO_CORES! ccnl-core/include/ccnl-sockunion.h:/*...

I'm wondering if we should preserve ndn2013 or integrate 0.3 and update the parts in code where necessary (so ndn2013 evolves to something like ndn2018)? Any thoughts @blacksheeep

Apparently, there is basically no implementation which supports it (yet). I can't estimate yet how much it differs from 0.2 and 0.3 is still subject to change. On the other...

We probably should also be aware that this is very likely to break the python scripts in ``src/py``.