On Sat, Apr 16, 2005 at 10:59:35AM -0400, David Magda wrote:
>
> On Apr 15, 2005, at 16:35, Juergen Schoenwaelder wrote:
>
> >P.S. The rollback capability in NetConf is optional and the list above
> > explains quite well why.
>
> Does the current draft have it as a MAY or as a SHOULD? (Really have to
> go through the draft, but only so many hours in a day.)
Rollback is a capability. NetConf has a core set of features and
capabilities. The idea is that additional capabilities may be added
over time and perhaps even by vendors.
> Perhaps if they made it a MUST it would spur companies to actually deal
> with this. I would hope that the writers of the RFC would at least look
> to the future on where you want to go in addition to simply where we
> are now. (Yes I am being idealistic here. :)
Making rollback a mandatory core feature means that many vendors will
not implement it since adding rollback may mean a big investment,
depending on your internal architecture. At the end, it boils down
to market decisions and what customers ask for. If customers are
willing to pay some extra $$ to get rollback support, vendors will
put it in. If customers do not care about the management interfaces
when they make investment decisions, the state of the art will not
improve.
/js
--
Juergen Schoenwaelder International University Bremen
<http://www.eecs.iu-bremen.de/> P.O. Box 750 561, 28725 Bremen, Germany
References:
|
|
