Re: [NGO] external module properties

On Mon, Apr 28, 2008 at 07:02:03AM -0700, Andy Bierman wrote:
> Juergen Schoenwaelder wrote:
> > On Sun, Apr 27, 2008 at 08:49:53AM -0700, Andy Bierman wrote:
> > 
> >> My point is that we need to thinking more holistically about the
> >> entire management system, which includes problems such as human factors
> >> and module life-cycle.
> > 
> > A data modeling language specification is the wrong place to address
> > human factors.
> 
> Really?  I thought YANG existed to provide the human-friendly data modeling
> interface that XSD and DSDL cannot provide.  It seems to me human factors
> are critical to CM.  Configuration errors are a big problem in real
> networks.  Providing an API and operational environment which is
> resistant to human-introduced errors is a very high priority to me.

You are mixing things and I stop responding to that.

> >> We tried the 'blinders-on' approach with SMING/EOS and that didn't
> >> work out so well.  Focusing on the DML and ignoring the protocol (or
> >> vice versa) leads to incomplete or broken solutions.
> > 
> > YANG is NETCONF very specific; it is by its very design a domain
> > specific language for NETCONF data models and not comparable to
> > SMING/EOS.
> 
> I think there are plenty of similarities and lessons to be learned
> from SMING and EOS.  I believe you wrote an RFC on the subject. ;-)

Go and read the document again and you will see a big argument against
protocol independent data modeling languages. (A revised version of
the ID will soon appear in IEEE Communications Magazine for those you
have access to it.) Now read my quote again and there will be
consistency.

> The YANG and 'Why YANG?' drafts cite the SMIng language as the
> starting point for YANG.

There is no contradiction with this in case you wanted to sound like
pointing out a contradiction. But even then, this has nothing to do
with the subject at hand in the first place.

> IMO, it is a bad idea to mix modules with and without versions.
> The namespace-stmt is mandatory because YANG is forcing good XML usage.
> Forcing the use of a version ID for good XML usage is no different.

I think someone already pointed out that the namespace is needed for
making NETCONF do the right thing.

/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/>
_______________________________________________
NGO mailing list
NGO@ietf.org
https://www.ietf.org/mailman/listinfo/ngo