Feature #3211
Updated by Yanbiao Li about 9 years ago
1. rename Remote Registration to Automatic Prefix Propagation.
REASON: the term "Remote" may confuse others, while "Automatic Propagation" impresses what this feature works.
2. eliminate two interfaces: registerPrefix / uregisterPrefix.
REASON: registration and unregistration processes are triggered by corresponding signals of Rib automatically, the entrances should be hided.
3. select the shortest available identity to register remotely, rather than the longest one.
REASON: to reduce the number of registered entries.
NOTE: no registration flag will be inherited from local RIB entries. The default setting (i.e, CHILD INHERIT) takes effect.
4. introduce a resendRegCommand method shared by refreshing, retrying or redoing (after hub connect) registrations and improve the mechanism.
REASON1: refreshing, retrying, redoing registrations all require to resend the registration commands.
REASON2: before resending commands, there may be new identities inserted or existing identities erased. This scenario was not covered before
5. introduce a RemoteRegisteredEntry class and a state machine to maintain registered entries.
6. maintain potential registered entries when there is no connectivity (fix Bug 2413)
7. correct the action when registration succeeds but the registered entry does not exist.
8. 7. adopt an expectational back-off strategy as the retry policy after registration fails, instead of performing limited number of retries.
9. 8. cover the case when unregistration succeeds but an entry with the same name exists.
10. 9. redesign the test suit.