Mikael Abrahamsson <[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.
> I would like to see a scheme where anything can be configured,
> including stuff which can be vendor-specific/proprietary so vendors can
> deploy new functionality quickly without going through a
DHCP is pretty good at this, as is Radius.
Using the DHCP option containers would make sense.
However, the important part of this discussion is to understand what kinds of
configuration parameters need to have fate sharing with the routing
information, and what kinds of things do not care.
I read the rest of the message, and I suggest that you start a new thread.
--
Michael Richardson <[email protected]>, Sandelman Software Works
pgp1gtTequudj.pgp
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
