Hi,

I have a few questions about this draft.
It's not that clear what problem it is trying to solve.

   YANG is also gaining wide acceptance as the de-facto standard
   modeling language in the broader industry.

Actually, YANG is a standards-track RFC so 'de-facto' is not correct.

In sec. 2 the difference between Network Element YANG Models and
Network Service YANG Models seems to imply that a service cannot
exist on just one NE.  I think the 2-layer framework is useful for
IETF purposes, but YANG models are not constrained to 2 layers
or just networking parameters. The whole draft seems very router-centric,
which is fine for the routing area, but not generic YANG.

I don't see the difference between a Proprietary YANG Model and
a Vendor Configuration Model.  This seems to place CLI at the same
level as YANG models.

      Vendor Configuration Model: It describes all configurable
      capabilities of the device and what device vendor exposes for
      configuration.  The vendor configuration model can be CLI or YANG-
      based.

IMO, the standards going forward need to focus on YANG, not schema-less CLI.
I don't see any role for proprietary CLI in the standards architecture.

The standard configuration model is a subset of vendor configuration model.

Isn't this backwards?  Seems like the total set of standard modules will
likely be a
superset of a particular vendor's configuration model.  Actually the
standard and
proprietary models may not overlap at all.

I think the 4 types of YANG models (or YANG modules?) are important
and we should have a common understanding on how they relate to each other.
I think that draft has a lot of potential to do that.

Not sure the terminology is right. We usually talk about one conceptual
data model
that is comprised of multiple YANG modules.  So this draft describes module
types
not really model types.


Andy


On Wed, Jun 3, 2015 at 11:58 AM, Benoit Claise <[email protected]> wrote:

>  FYI.
>
> Regards, Benoit
>
>
> -------- Forwarded Message --------  Subject: New Version Notification -
> draft-bogdanovic-netmod-yang-model-classification-03.txt  Date: Wed, 3
> Jun 2015 11:55:34 -0700  From: [email protected]  To:
> draft-bogdanovic-netmod-yang-model-classification.sheph...@ietf.org,
> [email protected],
> [email protected],
> [email protected],
> [email protected],
> [email protected], [email protected]
>
> A new version (-03) has been submitted for 
> draft-bogdanovic-netmod-yang-model-classification:https://www.ietf.org/internet-drafts/draft-bogdanovic-netmod-yang-model-classification-03.txt
>
>
> The IETF datatracker page for this Internet-Draft 
> is:https://datatracker.ietf.org/doc/draft-bogdanovic-netmod-yang-model-classification/
>
> Diff from previous 
> version:https://www.ietf.org/rfcdiff?url2=draft-bogdanovic-netmod-yang-model-classification-03
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> IETF Secretariat.
>
> .
>
>
>
>
>
> _______________________________________________
> netmod mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/netmod
>
>
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod

Reply via email to