Re: [YANG] new pyang errors

On Wed, Jan 23, 2008 at 09:25:56AM +0100, Ladislav Lhotka wrote:

> > a) ssh is not going to do that for me anytime soon
> 
> It's important that raw ssh works in principle but let's face it -
> reading and typing NETCONF XML stuff via stdin/stdout is only for
> masochists.

Perhaps real operators are masochists. Seriously, the amount of
existing scripting code using CLI interfaces is huge. This is not
going to go away. 

> > b) only the device really knows what has been touched
> 
> I'd like to make sure that my configurations work - as much as possible
> - even after the device has been replaced by another brand.

There is no contradiction between these two statements so I guess you
agree with my statement. ;-)

> > c) configuration will always be to some extend proprietary; so your
> >    app needs to understand all the proprietary stuff of all your devices
> 
> I don't agree - the whole NETCONF then wouldn't make much sense. That
> "some extent" must be rather minor IMO.

It is an illusion to believe that all router vendors will ship exactly
the same feature set. Whether the proprietary configuration knobs will
be 1% or 100% we don't know - but it will exist.

> > d) SNMP failed badly in this space, partly because of b) and c)
> 
> Avoiding hidden assumptions cannot make the situation worse, only
> better.

I am not sure which hidden assumptions you have in mind.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>

_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang