Re: [Netconf] Draft Charter Proposal for NETCONF WG


On 03/03/2017 16:39, Ladislav Lhotka wrote:
> "Eric Voit (evoit)" <evoit@cisco.com> writes:
>
>
>> An example here would be a data plane box (e.g. BNG) which spins up multiple VMs to handle its control plane session establishment.
>>
>> An operator doesn't want external systems to individually address
>> every control plane VM.  Rather they want a YANG model for this
>> logical+physical combination.  In this case each VM might use Peer
>> (data) Mount to build a multi-device abstraction.  BTW: doing it this
>> way also allows the same mounted YANG object data to be addressably
>> exposed for each VM without requiring another YANG model to be made.
> I think this can be mostly accomplished with the "inline" approach of
> schema mount (which in fact is a data mount and probably very similar to
> the concept of peer mount).
>
> IMO, what we are missing in terms of data modelling is really something
> like "device-less abstraction". I'd like to have a data modelling
> language or framework that would allow for saying: this is the complete
> data model, go and implement it (or let tools generate some code from
> it). Paradoxically, YANG isn't very good at this: we can write YANG
> modules but in order to combine them into coherent wholes we need to
> rely on some device to provide state data. Even with augments we have to
> assume that any device implementing an augmenting module will also
> implement the augmented module.
Could this be solved with YANG packages?  I.e. not only listing a set of 
modules, but also listing the set of modules that would be expected to 
be implemented for each of the mount points specified in those modules?

Rob


>
> Lada
>
>> Eric
>>
>>> but I think that device-less abstraction is also worth
>>> considering: apart from the particular client-server session context, there
>>> appears to be a need for specifying (and standardizing) more complex data
>>> models consisting of multiple modules, and augments (that are used for this
>>> purpose e.g. in RFC 8022) are sometimes insufficient.
>>>
>>> Lada
>>>
>>>> Eric
>>>>
>>>>
>>>> Lada
>>>>
>>>>
>>>> Andy
>>>>
>>>>
>>>>
>>>>> Tom Petch
>>>>>
>>>>>> /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/>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Netconf mailing list
>>>>>> Netconf@ietf.org<mailto:Netconf@ietf.org>
>>>>>> https://www.ietf.org/mailman/listinfo/netconf
>>>>> _______________________________________________
>>>>> Netconf mailing list
>>>>> Netconf@ietf.org<mailto:Netconf@ietf.org>
>>>>> https://www.ietf.org/mailman/listinfo/netconf
>>>> --
>>>> Ladislav Lhotka, CZ.NIC Labs
>>>> PGP Key ID: 0xB8F92B08A9F76C67
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Netconf mailing list
>>>> Netconf@ietf.org<mailto:Netconf@ietf.org>
>>>> https://www.ietf.org/mailman/listinfo/netconf
>>>>
>>> --
>>> Ladislav Lhotka, CZ.NIC Labs
>>> PGP Key ID: 0xB8F92B08A9F76C67