[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: text format of configurations
- To: Joe Provo <crimson@gweep.net>
- Subject: Re: text format of configurations
- From: john heasley <heas@shrubbery.net>
- Date: Tue, 26 Jun 2001 10:07:35 -0700
- Cc: ops-nm@ops.ietf.org
- Delivery-date: Tue, 26 Jun 2001 10:07:52 -0700
- Envelope-to: ops-nm-data@psg.com
- User-Agent: Mutt/1.2.5i
Tue, Jun 26, 2001 at 10:11:35AM -0400, Joe Provo:
> On Tue, Jun 26, 2001 at 12:04:45AM -0700, Bill Woodcock wrote:
> [snip]
> heas> - it MUST be possible to determine the FULL configuration of a box.
> heas> ie: NO hidden "defaults". if 'ip directed-broadcast' is the
> heas> default, a 'show config' option MUST exist that will display that
> heas> in the o/p (ascii or XML).
>
> > Hmmm. In principle I like this, but it could get awfully bulky awfully
> > fast. There are a _lot_ of defaults in some configs. Perhaps required
> > support for a "super verbose" version of "show config"? Something like
> > "show config full" or "show config all"?
>
> Perhaps verbosity to be set a la the suggested verbosity in the
> communications protocol itself; modal action where vendor- (or hardware-
> or software-version-) implicit defaults were expressed or supressed until
> toggled the other way? CF 'verbose' in the old infocom games... :-)
>
> This also gives a potential point for a 'complicance' (or
> 'legacy-compatibility') toggle. Some vendors may be highly resistant to
> breaking/reworking their internally-developed tools. Akin to 'aaa
> new-model' & its lack in cisco-land, "output (legacy|ietf|ietf-verbose)"?
they will be very energetic, if say, folks stop buying because it is
not "compliant".