NFD

what should happen when a hostname resolves to multiple IP addresses? also may be a mix of ipv4 and ipv6 addresses. John DeHart had this problem on the lip6 node.

The client must decide which IP to use prior to sending faces/create command.
The client may opt to send the command for one IP first. If face creation fails, the client can then send another command for a different IP.

Notice is sent to ndn-app ndn-lib nfd-dev.

This change cannot happen (merge) before Dec 04 12:00 UTC.

Not sure I understand this task correctly...
This task requires the controller to verify if the FaceUri is canonical. So this job should be done in the ndn-cxx.

Also please let me know how to update NFD Developer Guide?

This task requires the controller to verify if the FaceUri is canonical. So this job should be done in the ndn-cxx.

NO. This Task is to modify FaceManager so that non-canonical FaceUri is rejected with code 400.

Also please let me know how to update NFD Developer Guide?

See #1611.

NFD Developer Guide is already updated and committed to git@git.irl.cs.ucla.edu:papers/nfd-docs.git, need feedback.

nfd-docs commit is not correctly uploaded. HEAD is at 4e440922c6a2e56d9892f16321c2cd34f58c28a1 updated on Nov 19.

Sorry about incorrect submission.

Please tell me what command I should use to commit the updates: git push, git push origin HEAD:refs/for/master, or other command?

nfd-docs is a regular git repository, so git push origin master should be used for uploading.

nfd-docs upadtes committed.

Since someone is asking, I'll explain the rationale of requiring canonical FaceUri in faces/create: canonization is not the responsibility of NFD.

• NFD's responsibility is to forward NDN packets in NDN network.
• A major part of FaceUri canonization is performing a DNS lookup.
• DNS resolution is performed in IP network, and it can sometimes get messy and complex.
• DNS resolution routines in standard libraries are blocking; calling a blocking function in single-threaded NFD is bad. Third party libraries can offer non-blocking DNS resolution, but they increase the complexity of NFD.

In addition, face query operation (see FaceMgmt) requires canonical FaceUris.

• It's difficult or even impossible to compare two non-canonical FaceUris.
• Performing FaceUri canonization incurs all problems above.
• The same non-canonical FaceUri may resolve to different canonical FaceUris overtime, eg. due to DNS round-robin.

Requiring canonical FaceUri makes NFD simpler, and moves the complexity of DNS resolution to the client.