NFD

This is a small change, and MAY be completed without waiting for #2107 completion.

20150821 conference call decides that this doesn't need to wait for Dispatcher. Yanbiao agrees to resolve conflicts in ControlParameters when they happen.

@Yukai Can you finish updating the outstanding commits in gerrit by noon tomorrow? I don't like that we have dragged this issue up until the release (noon tomorrow) and I have to add disclaimer that even though we have support, but one cannot use it because management is missing for now... If you need help, I and other guys will be willing to help.

Reply to note-12:

Even if #2991 is done, it doesn't mean permface is ready for use. #2993 and #2994 are needed as well.

Release 0.3.4 is a snapshot release which includes whatever is available. The release is not a reason to rush any implementation.

Can you give me some guides about unit tests under ndn-cxx? Thanks.

I may need some helps when I doing unit test on ndn-cxx. Here are some error messages:

Running 607 test cases...

../tests/unit-tests/util/dns.t.cpp(59): fatal error in "Asynchronous": Resolved to 92.242.140.2, but should have failed

../tests/unit-tests/util/face-uri.t.cpp(87): error in "CanonizeUdpV4": udp4://invalid.invalid should fail

../tests/unit-tests/util/face-uri.t.cpp(88): error in "CanonizeUdpV4": check tc->m_expectedUri == canonicalUri.toString() failed [ != udp4://92.242.140.2:6363]

../tests/unit-tests/util/face-uri.t.cpp(87): error in "CanonizeTcpV4": tcp4://invalid.invalid should fail

../tests/unit-tests/util/face-uri.t.cpp(88): error in "CanonizeTcpV4": check tc->m_expectedUri == canonicalUri.toString() failed [ != tcp4://92.242.140.2:6363]

How can I fix these errors?

Answer to note-15:

You may be using a misbehaving/malicious DNS server.
If there is no other failure, you may ignore these errors.

@Yukai Some ISPs provide "misbehaved" caching DNS resolvers that return bogus IP address of internal "search" engine, instead of failing to resolve the domain name. In my case, TimeWarner did that, so I configured my router's DHCP to use Google's DNS. I guess COX is also doing this.

You can either switch your DNS settings to use different caching resolver or, as Junxiao suggested, ignore these specific errors.