Lorenzo Colitti <[email protected]> wrote: > I would like the WG to spend some face time dealing with (making a > list of), things that need to be configured, which are not routes.
> (So, I would include prefixes in the list)
> I disagree that routes prefixes can be treated separately from routes,
> because one router's prefixes are every other router's routes (well,
> either that,or things don't work).
That's the point. We have prefixes for interfaces and we have routes, and
they could, in theory, be configured seperately, but as you have pointed out
repeatedly, it makes no sense to do so, because they need to fate share.
In theory, one could have a route that leads somewhere, but once you get
there, it happens that no hosts are using that prefix, for some reason.
The question is: what other things do we need to configure, which are not
routes? Do they fate share or not?
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] [email protected] http://www.sandelman.ca/ | ruby on rails [
--
Michael Richardson <[email protected]>, Sandelman Software Works
pgpCeUyhFlk0y.pgp
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
