On Thu, Apr 07, 2016 at 08:55:19AM +0000, Scharf, Michael (Nokia - DE) wrote:
> > I come at this from the classification angle, so my interest is if the
> > assumption that
> > a YANG model can only be classified as a network service model XOR a
> > network device model
> > according to the definitions in draft-ietf-netmod-yang-model-classification
> > (sections 2.1
> > and 2.2). Based on this discussion I take it that some models are intended
> > to be able to
> > serve in both roles. And we should make sure that it’s supported in our
> > catalog structure.
>
> Regarding the XOR assumption for classification:
>
> You may also want to think about YANG models that are NEITHER device NOR
> service models. For instance, what about RFC 6991? And I think other, more
> technical models presented this week may fall into a similar category
> ("generic"?).
>
RFC 6991 is not really defining a data model, while ietf-yang-types
and ietf-inet-types are both YANG modules they do not define any data
nodes that can be implemented. Lets look at RFC 6020bis:
o data model: A data model describes how data is represented and
accessed.
Anyway, the point is that RFC 6991 do not define any data nodes and
hence nothing that can be accessed. Perhaps it helps to import
terminology into the model classification document and to be explicit
that not all YANG modules define YANG data models.
/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/>
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
