NDN-CCL

Is there a planned date when the new NFD version with this breaking change will be put on the test bed?

This breaking change is coming in next NFD release, which is likely in Sep 2019.
PyNDN needs to encode to v0.3 by default now, so that it can work with both current and next version of NFD.

REMAP has no current support to update the CCL and CNL libraries - so right now it's not clear that this can happen in September. I'll be looking into a solution at ndncomm.

REMAP has no current support to update the CCL and CNL libraries

Are you saying CCL and CNL will no longer be updated, and are going to be abandoned?

This is an essential update. Although this issue is “blocking” #4567, ndn-cxx and NFD cannot wait forever.

We do not intend to abandon either library, but have no funding to do work on them, either, after the end of the CRI award and the limited scope of support on ICN-WEN. (I sent a reminder the PIs in mid-May about this.) I hope to discuss a resolution with folks at ndncomm - either we need to identify funding for REMAP to continue maintaining or find another maintainer. My strong preference is the former.

Just to clarify the scope of this issue... Based on what I heard months ago, all common client libraries fully support the new packet format. Therefore, this task should "simply" consists in switching the default encoding of Interest packets from v0.2 to v0.3, and possibly update some unit tests and related things to accommodate the new default. So it should be a relatively minor task.

It is in fact trivial. esp8266ndn's patch for ndn-cpp C is only one line change https://github.com/yoursunny/esp8266ndn/commit/7730f30910f5b337af2c577ef5dce6d694868a26 although not clean.

Breaking changes have been merged to ndn-cxx. CCL are now broken.

https://github.com/named-data/PyNDN2/pull/8

https://github.com/named-data/ndn-js/pull/78