ndnSIM

How about renaming the organization to just 'ndnSIM', if it's not taken?

I would like to keep strong association with named-data organization.

I assume this means that all developers/users have to adapt their repositories and dependencies to the new links?

Also, with these new names in place, will there be a system that tells me which versions of ndn-cxx/NFD/ndnSIM are compatible (e.g., if ndn-cxx gets updated).
Or can I assume that IF it is under this new repository name, it will always be consistent and compatible?

I will keep mirrors of repositories in old locations.

The new locations are specifically made for submodule integration of ndn-cxx and NFD into ndnSIM. So, this would significantly simplify issue with version compatibility, as there will be no moving parts unless there is an explicit update of ndnSIM.

I will try to keep documentation of what is the current base version of NFD/ndn-cxx as part of commit log and will create a changelog for that.