Project

General

Profile

Task #3568

Don't autoreg local site prefix

Added by Junxiao Shi over 3 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
RIB
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
3.00 h

Description

On NDN testbed, reconfigure nfd-autoreg so that it does not register local site prefix.

nfd-autoreg should still be used to register multicast prefixes such as /ndn/broadcast.

Rationale

Despite the availability of automatic prefix propagation, many applications are relying on inaccurate prefixes registered by nfd-autoreg because "it just works", which is causing forwarding performance degradation.

Disabling nfd-autoreg effectively forces applications to educate their users to enable automatic prefix propagation on end hosts.

Implication

Users must obtain certificates from ndncert and enable automatic prefix propagation on end hosts before publishing anything.

Before #2766, only certificates directly requested from ndncert can be used with automatic prefix propagation.

History

#1 Updated by Peter Gusev over 3 years ago

This will prevent ndncon users from discovering each other until #3513 is resolved. I'd wait till it's implemented and tested and then turn off autoreg.

#2 Updated by John DeHart over 3 years ago

Peter Gusev wrote:

This will prevent ndncon users from discovering each other until #3513 is resolved. I'd wait till it's implemented and tested and then turn off autoreg.

nfd-autoreg will still run and configure /ndn/multicast and /ndn/broadcast.
Won't that take care of the discovery needed?

That and Alex's work-around for the prefix for a user of ndncon

#3 Updated by Junxiao Shi over 3 years ago

This change does not affect NdnCon.

  • #3513-19 workaround allows the user prefix to fall under an identity compatible with automatic prefix propagation.
  • Multicast prefixes are still registered with nfd-autoreg.

#4 Updated by Jeff Burke over 3 years ago

Can we still have a flag day announced to ndn lists and instructions for mitigating impact on old apps? (With plenty of time...?)

#5 Updated by John DeHart over 3 years ago

My plan was to wait for agreement from the NdnCon folks that this would not affect their application and
then make an announcement to the mailing list with a date for the change to be put in place.

Are Peter and Jeff convinced that there will be no impact on their efforts?

#6 Updated by Junxiao Shi over 3 years ago

Notice is sent to ndn operators ndn-app.

#7 Updated by Peter Gusev over 3 years ago

@Junxiao, can you please give me a link on how users should "enable automatic prefix propagation on end hosts before publishing anything.". If we proceed with this change before #3513 resolution, I have to provide information on how to ensure discoverability for users.

#8 Updated by Junxiao Shi over 3 years ago

Answer to note-7:

Default NFD configuration file has auto_prefix_propagate section already enabled.

User needs to request a testbed certificate, and import this certificate into NFD's KeyChain so it's accessible by automatic prefix propagator.
See the announcement under "to migrate your application" step 1 and 2 for procedure if NFD is installed from Ubuntu package.
For NFD installed from source code, NFD's KeyChain is same as user's KeyChain, so only step 1 is needed.

This procedure is needed with or without #3513.

#9 Updated by Junxiao Shi over 3 years ago

Before #2766, only certificates directly requested from ndncert can be used with automatic prefix propagation.

An implication from this specific point is:
If a user installs the same certificate on multiple end hosts, in case those end hosts send prefix registration requests at the same time, some prefix registrations might fail.

SignedInterestProcessing suggests not to share the key/certificate across end hosts, but request one ndncert certificate for each end host; the same person having multiple certificates is permitted under testbed policy.

#10 Updated by John DeHart over 3 years ago

I plan to update the Testbed nodes' configurations on June 1st.

#11 Updated by Junxiao Shi over 3 years ago

  • Status changed from New to Resolved

http://www.lists.cs.ucla.edu/mailman/private/ndn/2016-June/001218.html

the nfd-autoreg configuration change is done.
All nodes that are currently up have been updated and nfd-autoreg restarted.

#12 Updated by Junxiao Shi over 3 years ago

  • % Done changed from 0 to 100

#13 Updated by Junxiao Shi about 3 years ago

  • Status changed from Resolved to Closed

For information: Let the World Reach Your NFD can help an end user to setup Automatic Prefix Propagation.

Also available in: Atom PDF