3 ms·
The thing is that routes aren't (usually) hard-coded anywhere: they're computed by each individual device, and while requests to perform the computation can be
by gaius 18y ago
The thing is that routes aren't (usually) hard-coded anywhere: they're computed by each individual device, and while requests to perform the computation can be triggered upstream, there's nowhere that has a "one true" view of the network.
You could theoretically say "at time T1, everyone save your current tables" and then sometime later (when you were confident it had propagated everywhere) say "at time T2, revert back to your tables as of T1" but you'd have to assume that no devices had joined or left in the intervening time; in practice the only way back is to trigger a new computation and return to an approximation of the earlier state.