RE: (multi6) requirements draft comments

["Christian Huitema" <huitema@windows.microsoft.com>]

> What's more interesting is to think about what happens when there's a
> failure. This is *not* a situation that K-K talks about - they are
simply
> analyzing the most efficient naming hiearchy for optimal (in terms of
> minimum table size) routing.

Isn't it the case that, in order to maintain optimality in the face of a
graph change, you have to entirely revisit your aggregation structure,
which would be akin to renumbering the Internet?

-- Christian Huitema