Re: [NGO] external module properties

Jon Saperia wrote:
>  From an application perspective, I would like to see both Version and 
> Namespace as a standard/required part of the modules.  I think the need 
> for version is pretty obvious, Name space is an important discriminator 
> for management applications.

Agreed.

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.

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.

Of course the namespace URI is mandatory, because it is needed
to properly implement the NETCONF protocol.  The 'YANG philosphy'
(whatever that is) has nothing to do with it.  Likewise, the
revision date is needed to properly implement NETCONF applications.

YANG is not decoupled from NETCONF, and NETCONF is not decoupled
from the actual CM problem space.  One needs to consider that sometimes
CLRs are really CBRs, and important for real interoperability.

> /jon

Andy

Andy

_______________________________________________
NGO mailing list
NGO@ietf.org
https://www.ietf.org/mailman/listinfo/ngo